search

ugoviti / izpbx

izPBX is a Turnkey Cloud Native Telephony System powered by Asterisk Engine and FreePBX Management GUI
GNU General Public License v3.0
168 stars 69 forks source link

izpbx stop frequenly #64

Closed fukemy closed 3 months ago

fukemy commented 3 months ago

I saw izpbx stop frequenly after a little time, and restart, i can not check a bug in logs, but I only see this line: 2024-04-09 03:26:41,169 INFO exited: izpbx (exit status 1; not expected)

here is the full log:

=> Starting container izPBX Cloud Native Telephony System -> izpbx-asterisk:20.16.11 (build:109 commit:eb6e874 date:2024-01-06)
===============================================================================
=> Executing izpbx-asterisk hooks:
--> fixing supervisord config file...
---> RHEL Linux based distro detected
=> Persistent storage path detected... relocating and reconfiguring system data and configuration files using basedir: '/data'
--> [01/17] INFO: [/etc/dnsmasq.d] detected directory data override path: '/data/etc/dnsmasq.d'
----------> INFO: [/etc/dnsmasq.d] renaming '/etc/dnsmasq.d' to '/etc/dnsmasq.d.dist'
----------> INFO: [/etc/dnsmasq.d] symlinking '/etc/dnsmasq.d' to '/data/etc/dnsmasq.d'
----------> INFO: [/etc/dnsmasq.d.dist] data dir '/data/etc/dnsmasq.d' is already initialized... skipping data initialization
--> [02/17] INFO: [/var/log/fail2ban] detected directory data override path: '/data/var/log/fail2ban'
----------> INFO: [/var/log/fail2ban] renaming '/var/log/fail2ban' to '/var/log/fail2ban.dist'
----------> INFO: [/var/log/fail2ban] symlinking '/var/log/fail2ban' to '/data/var/log/fail2ban'
log_it: (CRON 2580) INFO (Shutting down)
grep: /data/etc/asterisk/extensions_additional.conf: No such file or directory
----------> INFO: [/var/log/fail2ban.dist] data dir '/data/var/log/fail2ban' is already initialized... skipping data initialization
--> [03/17] INFO: [/var/log/asterisk] detected directory data override path: '/data/var/log/asterisk'
----------> INFO: [/var/log/asterisk] renaming '/var/log/asterisk' to '/var/log/asterisk.dist'
----------> INFO: [/var/log/asterisk] symlinking '/var/log/asterisk' to '/data/var/log/asterisk'
----------> INFO: [/var/log/asterisk.dist] data dir '/data/var/log/asterisk' is already initialized... skipping data initialization
--> [04/17] INFO: [/etc/asterisk] detected directory data override path: '/data/etc/asterisk'
----------> INFO: [/etc/asterisk] renaming '/etc/asterisk' to '/etc/asterisk.dist'
----------> INFO: [/etc/asterisk] symlinking '/etc/asterisk' to '/data/etc/asterisk'
----------> INFO: [/etc/asterisk.dist] data dir '/data/etc/asterisk' is already initialized... skipping data initialization
--> [05/17] INFO: [/var/log/httpd] detected directory data override path: '/data/var/log/httpd'
----------> INFO: [/var/log/httpd] renaming '/var/log/httpd' to '/var/log/httpd.dist'
----------> INFO: [/var/log/httpd] symlinking '/var/log/httpd' to '/data/var/log/httpd'
----------> INFO: [/var/log/httpd.dist] data dir '/data/var/log/httpd' is already initialized... skipping data initialization
--> [06/17] INFO: [/home/asterisk] detected directory data override path: '/data/home/asterisk'
----------> INFO: [/home/asterisk] renaming '/home/asterisk' to '/home/asterisk.dist'
----------> INFO: [/home/asterisk] symlinking '/home/asterisk' to '/data/home/asterisk'
----------> INFO: [/home/asterisk.dist] data dir '/data/home/asterisk' is already initialized... skipping data initialization
--> [07/17] INFO: [/var/lib/fail2ban] detected directory data override path: '/data/var/lib/fail2ban'
----------> INFO: [/var/lib/fail2ban] renaming '/var/lib/fail2ban' to '/var/lib/fail2ban.dist'
----------> INFO: [/var/lib/fail2ban] symlinking '/var/lib/fail2ban' to '/data/var/lib/fail2ban'
----------> INFO: [/var/lib/fail2ban.dist] data dir '/data/var/lib/fail2ban' is already initialized... skipping data initialization
--> [08/17] INFO: [/root] detected directory data override path: '/data/root'
----------> INFO: [/root] renaming '/root' to '/root.dist'
----------> INFO: [/root] symlinking '/root' to '/data/root'
----------> INFO: [/root.dist] data dir '/data/root' is already initialized... skipping data initialization
--> [09/17] INFO: [/var/spool/asterisk] detected directory data override path: '/data/var/spool/asterisk'
----------> INFO: [/var/spool/asterisk] renaming '/var/spool/asterisk' to '/var/spool/asterisk.dist'
----------> INFO: [/var/spool/asterisk] symlinking '/var/spool/asterisk' to '/data/var/spool/asterisk'
----------> INFO: [/var/spool/asterisk.dist] data dir '/data/var/spool/asterisk' is already initialized... skipping data initialization
--> [10/17] INFO: [/usr/local/fop2] detected directory data override path: '/data/usr/local/fop2'
----------> INFO: [/usr/local/fop2] renaming '/usr/local/fop2' to '/usr/local/fop2.dist'
----------> INFO: [/usr/local/fop2] symlinking '/usr/local/fop2' to '/data/usr/local/fop2'
----------> INFO: [/usr/local/fop2.dist] data dir '/data/usr/local/fop2' is already initialized... skipping data initialization
--> [11/17] INFO: [/var/www] detected directory data override path: '/data/var/www'
----------> INFO: [/var/www] renaming '/var/www' to '/var/www.dist'
----------> INFO: [/var/www] symlinking '/var/www' to '/data/var/www'
----------> INFO: [/var/www.dist] data dir '/data/var/www' is already initialized... skipping data initialization
--> [12/17] INFO: [/var/lib/tftpboot] detected directory data override path: '/data/var/lib/tftpboot'
----------> INFO: [/var/lib/tftpboot] renaming '/var/lib/tftpboot' to '/var/lib/tftpboot.dist'
----------> INFO: [/var/lib/tftpboot] symlinking '/var/lib/tftpboot' to '/data/var/lib/tftpboot'
----------> INFO: [/var/lib/tftpboot.dist] data dir '/data/var/lib/tftpboot' is already initialized... skipping data initialization
--> [13/17] INFO: [/var/spool/cron] detected directory data override path: '/data/var/spool/cron'
----------> INFO: [/var/spool/cron] renaming '/var/spool/cron' to '/var/spool/cron.dist'
----------> INFO: [/var/spool/cron] symlinking '/var/spool/cron' to '/data/var/spool/cron'
----------> INFO: [/var/spool/cron.dist] data dir '/data/var/spool/cron' is already initialized... skipping data initialization
--> [14/17] INFO: [/var/lib/dnsmasq] detected directory data override path: '/data/var/lib/dnsmasq'
----------> INFO: [/var/lib/dnsmasq] renaming '/var/lib/dnsmasq' to '/var/lib/dnsmasq.dist'
----------> INFO: [/var/lib/dnsmasq] symlinking '/var/lib/dnsmasq' to '/data/var/lib/dnsmasq'
----------> INFO: [/var/lib/dnsmasq.dist] data dir '/data/var/lib/dnsmasq' is already initialized... skipping data initialization
--> [15/17] INFO: [/var/lib/asterisk] detected directory data override path: '/data/var/lib/asterisk'
----------> INFO: [/var/lib/asterisk] renaming '/var/lib/asterisk' to '/var/lib/asterisk.dist'
----------> INFO: [/var/lib/asterisk] symlinking '/var/lib/asterisk' to '/data/var/lib/asterisk'
----------> INFO: [/var/lib/asterisk.dist] data dir '/data/var/lib/asterisk' is already initialized... skipping data initialization
--> [16/17] INFO: [/etc/amportal.conf] file data override detected: default:[/etc/amportal.conf] custom:[/data/etc/amportal.conf]
----------> INFO: [/etc/amportal.conf] renaming to '/etc/amportal.conf.dist'... 
----------> INFO: [/etc/amportal.conf] symlinking '/etc/amportal.conf' to '/data/etc/amportal.conf'
--> [17/17] INFO: [/etc/freepbx.conf] file data override detected: default:[/etc/freepbx.conf] custom:[/data/etc/freepbx.conf]
----------> INFO: [/etc/freepbx.conf] renaming to '/etc/freepbx.conf.dist'... 
----------> INFO: [/etc/freepbx.conf] symlinking '/etc/freepbx.conf' to '/data/etc/freepbx.conf'
--> verifying files permissions
---> fixing owner: '/var/lib/tftpboot'
=> Setting up MSMTP as (default) sendmail replacement
--> forwarding all emails to: 
=> Disabling postfix service... because POSTFIX_ENABLED=false
=> Enabling cron service... because CRON_ENABLED=true
--> configuring cron service...
---> fixing permissions: '/var/spool/cron'
=> Enabling fail2ban service... because FAIL2BAN_ENABLED=true
--> configuring fail2ban service...
--> reconfiguring Fail2ban settings...
=> Enabling httpd service... because HTTPD_ENABLED=true
--> configuring httpd service...
--> setting Apache ServerName to docker-desktop
--> configuring Apache VirtualHosting and creating empty /etc/httpd/conf.d/virtual.conf file
=> Disabling asterisk service... because ASTERISK_ENABLED=false
=> Enabling izpbx service... because IZPBX_ENABLED=true
--> configuring izpbx service...
---> verifing FreePBX configurations
---> using '/data' as basedir for FreePBX install
---> fixing permissions for: ASTLOGDIR=/var/log/asterisk
---> fixing permissions for: ASTETCDIR=/etc/asterisk
---> fixing permissions for: ASTSPOOLDIR=/var/spool/asterisk
---> fixing permissions for: ASTVARLIBDIR=/var/lib/asterisk
---> configuring FreePBX ODBC
---> INFO: found '/data/.initialized' file - Detected installed FreePBX version: 16
---> reconfiguring '/etc/freepbx.conf'
---> FIXME: applying workarounds for FreePBX broken modules and configs...
---> fixing directory system paths in db configuration...
---> reconfiguring FreePBX Advanced Settings if needed...
---> reconfiguring advanced setting: HTTPBINDPORT=8088
The setting HTTPBINDPORT was not found!
---> reconfiguring advanced setting: PHPTIMEZONE=Europe/Rome
The setting PHPTIMEZONE was not found!
---> reconfiguring advanced setting: TONEZONE=it
The setting TONEZONE was not found!
---> reconfiguring FreePBX SIP Settings if needed...
---> reconfiguring sip setting: tcpport-0.0.0.0=5060
Exception: Unable to locate the FreePBX BMO Class 'Sipsettings'A required module might be disabled or uninstalled. Recommended steps (run from the CLI): 1) fwconsole ma install sipsettings 2) fwconsole ma enable sipsettings in file /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php on line 212
Stack trace:
  1. Exception->() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:212
  2. FreePBX\Self_Helper->loadObject() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:106
  3. FreePBX\Self_Helper->autoLoad() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:37
  4. FreePBX\Self_Helper->__get() Standard input code:1
---> reconfiguring sip setting: rtpend=20000
Exception: Unable to locate the FreePBX BMO Class 'Sipsettings'A required module might be disabled or uninstalled. Recommended steps (run from the CLI): 1) fwconsole ma install sipsettings 2) fwconsole ma enable sipsettings in file /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php on line 212
Stack trace:
  1. Exception->() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:212
  2. FreePBX\Self_Helper->loadObject() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:106
  3. FreePBX\Self_Helper->autoLoad() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:37
  4. FreePBX\Self_Helper->__get() Standard input code:1
---> reconfiguring sip setting: bindport=5160
Exception: Unable to locate the FreePBX BMO Class 'Sipsettings'A required module might be disabled or uninstalled. Recommended steps (run from the CLI): 1) fwconsole ma install sipsettings 2) fwconsole ma enable sipsettings in file /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php on line 212
Stack trace:
  1. Exception->() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:212
  2. FreePBX\Self_Helper->loadObject() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:106
  3. FreePBX\Self_Helper->autoLoad() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:37
  4. FreePBX\Self_Helper->__get() Standard input code:1
---> reconfiguring sip setting: udpport-0.0.0.0=5060
Exception: Unable to locate the FreePBX BMO Class 'Sipsettings'A required module might be disabled or uninstalled. Recommended steps (run from the CLI): 1) fwconsole ma install sipsettings 2) fwconsole ma enable sipsettings in file /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php on line 212
Stack trace:
  1. Exception->() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:212
  2. FreePBX\Self_Helper->loadObject() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:106
  3. FreePBX\Self_Helper->autoLoad() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:37
  4. FreePBX\Self_Helper->__get() Standard input code:1
---> reconfiguring sip setting: rtpstart=10000
Exception: Unable to locate the FreePBX BMO Class 'Sipsettings'A required module might be disabled or uninstalled. Recommended steps (run from the CLI): 1) fwconsole ma install sipsettings 2) fwconsole ma enable sipsettings in file /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php on line 212
Stack trace:
  1. Exception->() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:212
  2. FreePBX\Self_Helper->loadObject() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:106
  3. FreePBX\Self_Helper->autoLoad() /data/var/www/html/admin/libraries/BMO/Self_Helper.class.php:37
  4. FreePBX\Self_Helper->__get() Standard input code:1
=> Disabling zabbix service... because ZABBIX_ENABLED=false
=> Disabling fop2 service... because FOP2_ENABLED=false
=> Disabling ntp service... because NTP_ENABLED=false
=> Disabling dnsmasq service... because DNSMASQ_ENABLED=false
=> Enabling Remote XML PhoneBook support
-------------------------------------------------------------------------------
=> Executing izpbx-asterisk entrypoint command: supervisord -c /etc/supervisord.conf
===============================================================================
2024-04-09 03:29:05,574 INFO Included extra file "/etc/supervisord.d/asterisk.ini" during parsing
2024-04-09 03:29:05,575 INFO Included extra file "/etc/supervisord.d/cron.ini" during parsing
2024-04-09 03:29:05,575 INFO Included extra file "/etc/supervisord.d/dnsmasq.ini" during parsing
2024-04-09 03:29:05,576 INFO Included extra file "/etc/supervisord.d/fail2ban.ini" during parsing
2024-04-09 03:29:05,576 INFO Included extra file "/etc/supervisord.d/fop2.ini" during parsing
2024-04-09 03:29:05,576 INFO Included extra file "/etc/supervisord.d/httpd.ini" during parsing
2024-04-09 03:29:05,576 INFO Included extra file "/etc/supervisord.d/izpbx.ini" during parsing
2024-04-09 03:29:05,576 INFO Included extra file "/etc/supervisord.d/ntp.ini" during parsing
2024-04-09 03:29:05,576 INFO Included extra file "/etc/supervisord.d/postfix.ini" during parsing
2024-04-09 03:29:05,576 INFO Included extra file "/etc/supervisord.d/zabbix.ini" during parsing
2024-04-09 03:29:05,577 INFO Set uid to user 0 succeeded
2024-04-09 03:29:05,589 INFO RPC interface 'supervisor' initialized
2024-04-09 03:29:05,590 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-04-09 03:29:05,591 INFO supervisord started with pid 1
2024-04-09 03:29:06,610 INFO spawned: 'izpbx-watchdog_0' with pid 2569
2024-04-09 03:29:06,617 INFO spawned: 'cron' with pid 2571
2024-04-09 03:29:06,622 INFO spawned: 'fail2ban' with pid 2573
2024-04-09 03:29:06,627 INFO spawned: 'httpd' with pid 2575
2024-04-09 03:29:06,630 INFO spawned: 'izpbx' with pid 2577
READY
2024-04-09 03:29:07,761 INFO success: izpbx-watchdog_0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-09 03:29:07,762 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-09 03:29:07,762 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-09 03:29:07,762 INFO success: izpbx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Server ready
2024-04-09 03:29:11,966 INFO success: fail2ban entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2024-04-09 03:29:25,999 INFO reaped unknown pid 2907 (exit status 0)
2024-04-09 03:30:07,415 INFO exited: izpbx (exit status 1; not expected)
2024-04-09 03:30:07,441 INFO spawned: 'izpbx' with pid 3547
2024-04-09 03:30:07,443 WARN received SIGQUIT indicating exit request
2024-04-09 03:30:07,445 INFO waiting for izpbx-watchdog_0, cron, fail2ban, httpd, izpbx to die
2024-04-09 03:30:08,447 INFO success: izpbx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-09 03:30:10,454 INFO waiting for izpbx-watchdog_0, cron, fail2ban, httpd, izpbx to die
2024-04-09 03:30:10,458 INFO reaped unknown pid 3675 (terminated by SIGTERM)
2024-04-09 03:30:10,458 INFO reaped unknown pid 3671 (terminated by SIGTERM)
Asterisk not currently running
Running FreePBX shutdown...
2024-04-09 03:30:11,378 INFO stopped: izpbx (exit status 0)
2024-04-09 03:30:11,512 INFO stopped: httpd (exit status 0)
2024-04-09 03:30:13,010 INFO stopped: fail2ban (exit status 0)
2024-04-09 03:30:14,021 INFO waiting for izpbx-watchdog_0, cron to die
2024-04-09 03:30:14,029 INFO stopped: cron (exit status 0)
2024-04-09 03:30:15,041 INFO stopped: izpbx-watchdog_0 (terminated by SIGTERM)
=> Starting container izPBX Cloud Native Telephony System -> izpbx-asterisk:20.16.11 (build:109 commit:eb6e874 date:2024-01-06)
===============================================================================
fukemy commented 3 months ago

I found this line after restart:

In Start.class.php line 193:

  Unable to connect to Asterisk. Did it start?  

start [--pre] [--post] [--skipchown] [--] [<args>]...
Terminated
log_it: (CRON 2507) INFO (Shutting down)
2024-04-09 03:45:20,030 INFO exited: izpbx (exit status 1; not expected)
2024-04-09 03:45:20,037 INFO spawned: 'izpbx' with pid 3483
2024-04-09 03:45:20,038 WARN received SIGQUIT indicating exit request
2024-04-09 03:45:20,039 INFO waiting for izpbx-watchdog_0, cron, fail2ban, httpd, izpbx to die
2024-04-09 03:45:21,041 INFO success: izpbx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-09 03:45:23,048 INFO waiting for izpbx-watchdog_0, cron, fail2ban, httpd, izpbx to die
2024-04-09 03:45:23,052 INFO reaped unknown pid 3611 (terminated by SIGTERM)
2024-04-09 03:45:23,052 INFO reaped unknown pid 3607 (terminated by SIGTERM)
Asterisk not currently running
Running FreePBX shutdown...
ugoviti commented 3 months ago

Windows Docker Desktop is not a tested system... if you succeed I'm happy, but this is not guaranteed, I'm sorry. Check the section https://github.com/ugoviti/izpbx?tab=readme-ov-file#tested-systems-and-host-compatibility

Kind Regards

fukemy commented 3 months ago

Im using mac m1 to test, can u give some advices without tested system? I tried with my Ubuntu VM but I got other error with docker logs izpbx:

exec /entrypoint.sh: exec format error
ugoviti commented 3 months ago

I'm sorry but izPBX is x86_64 arch dependent, Apple M1 is ARM arch, so it's untested right now.

fukemy commented 2 months ago

hello, I tested on Ubuntu 22.04 but still got same problem. Can you help?

=> Executing izpbx-asterisk entrypoint command: supervisord -c /etc/supervisord.conf
===============================================================================
+ exec supervisord -c /etc/supervisord.conf
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/asterisk.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/cron.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/dnsmasq.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/fail2ban.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/fop2.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/httpd.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/izpbx.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/ntp.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/postfix.ini" during parsing
2024-04-12 04:29:23,137 INFO Included extra file "/etc/supervisord.d/zabbix.ini" during parsing
2024-04-12 04:29:23,137 INFO Set uid to user 0 succeeded
2024-04-12 04:29:23,141 INFO RPC interface 'supervisor' initialized
2024-04-12 04:29:23,141 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-04-12 04:29:23,142 INFO supervisord started with pid 1
2024-04-12 04:29:24,145 INFO spawned: 'izpbx-watchdog_0' with pid 900
2024-04-12 04:29:24,147 INFO spawned: 'cron' with pid 901
2024-04-12 04:29:24,150 INFO spawned: 'fail2ban' with pid 902
2024-04-12 04:29:24,152 INFO spawned: 'httpd' with pid 903
2024-04-12 04:29:24,155 INFO spawned: 'izpbx' with pid 904
READY
debug flags enabled: misc
[901] cron started
log_it: (CRON 901) STARTUP (1.5.2)
log_it: (CRON 901) INFO (RANDOM_DELAY will be scaled with factor 24% if used.)
log_it: (CRON 901) INFO (running with inotify support)
log_it: (CRON 901) INFO (@reboot jobs will be run at computer's startup.)
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
2024-04-12 04:29:24,212 INFO exited: httpd (exit status 1; not expected)
2024-04-12 04:29:24,285 fail2ban                [902]: ERROR   Failed during configuration: Have not found any log file for apache-auth jail
2024-04-12 04:29:24,291 fail2ban                [902]: ERROR   Async configuration of server failed
2024-04-12 04:29:24,305 INFO exited: fail2ban (exit status 255; not expected)
2024-04-12 04:29:25,306 INFO success: izpbx-watchdog_0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-12 04:29:25,306 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-12 04:29:25,308 INFO spawned: 'fail2ban' with pid 1006
2024-04-12 04:29:25,312 INFO spawned: 'httpd' with pid 1007
2024-04-12 04:29:25,312 INFO success: izpbx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-12 04:29:25,312 INFO reaped unknown pid 989 (exit status 0)
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
2024-04-12 04:29:25,365 INFO exited: httpd (exit status 1; not expected)
2024-04-12 04:29:25,426 fail2ban                [1006]: ERROR   Failed during configuration: Have not found any log file for apache-auth jail
2024-04-12 04:29:25,426 fail2ban                [1006]: ERROR   Async configuration of server failed
2024-04-12 04:29:25,435 INFO exited: fail2ban (exit status 255; not expected)
Starting Call Transfer Monitoring Service
Stopping Call Transfer Monitoring Service
Restarting Call Transfer Monitoring Service
2024-04-12 04:29:28,108 INFO spawned: 'fail2ban' with pid 1186
2024-04-12 04:29:28,111 INFO spawned: 'httpd' with pid 1187
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
2024-04-12 04:29:28,174 INFO exited: httpd (exit status 1; not expected)
2024-04-12 04:29:28,243 fail2ban                [1186]: ERROR   Failed during configuration: Have not found any log file for apache-auth jail
2024-04-12 04:29:28,246 fail2ban                [1186]: ERROR   Async configuration of server failed
2024-04-12 04:29:28,259 INFO exited: fail2ban (exit status 255; not expected)
2024-04-12 04:29:31,265 INFO spawned: 'fail2ban' with pid 1311
2024-04-12 04:29:31,269 INFO spawned: 'httpd' with pid 1312
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
2024-04-12 04:29:31,337 INFO exited: httpd (exit status 1; not expected)
2024-04-12 04:29:31,396 fail2ban                [1311]: ERROR   Failed during configuration: Have not found any log file for apache-auth jail
2024-04-12 04:29:31,396 INFO gave up: httpd entered FATAL state, too many start retries too quickly
2024-04-12 04:29:31,396 fail2ban                [1311]: ERROR   Async configuration of server failed
2024-04-12 04:29:31,404 INFO exited: fail2ban (exit status 255; not expected)
2024-04-12 04:29:31,404 WARN received SIGQUIT indicating exit request
2024-04-12 04:29:31,404 INFO waiting for izpbx-watchdog_0, cron, fail2ban, izpbx to die
2024-04-12 04:29:32,406 INFO gave up: fail2ban entered FATAL state, too many start retries too quickly
2024-04-12 04:29:34,409 INFO waiting for izpbx-watchdog_0, cron, izpbx to die
Terminated
2024-04-12 04:29:34,410 INFO reaped unknown pid 1002 (terminated by SIGTERM)
Asterisk not currently running
Running FreePBX shutdown...
ugoviti commented 2 months ago

Here you have already other service running in the sames ports (HTTP/80), you must use a VM or a host exclusively dedicated to izpbx.

kind regards