Bug #2046
Amahi 10 Sometimes it takes an extra reboot to get networking right
0%
Description
in amahi 9 we're seeing that sometimes there are some users that have issues with networking in the last stage, even sometimes after a reboot.
there are two possible alternative solutions:
1) if the user can type commands into the console or ssh into the box, issuing an hda-ctl-hup may help, possibly followed by a reboot
2) if the user cannot easily ssh or use the console, then a reboot or two may help re-set the settings and get networking in operation
We should really try to capture this in a system and diagnose it and fix it.
[incidentally, rather than sending them to support, we should send them here]
History
#1 Updated by bigfoot65 almost 5 years ago
Added link to bug in the Troubleshooting wiki page for Amahi 9.
https://wiki.amahi.org/index.php/Troubleshooting_Amahi_9
#2 Updated by visionnaire about 4 years ago
I'm having same/similar difficulties after installing Amahi 9 on Fedora 23 (minimal install, following official instructions).
Symptom:
Cannot access http://hda or http://IP_ADDRESS of my Amahi server from within local network.
Tried restarting hda service like described here and rebooting 2x but no luck, same result.
From another PC in same network:
MYPC:~ user$ curl hda
curl: (7) Failed to connect to hda port 80: Connection refused
PYPC:~ user$ curl 192.168.5.50
curl: (7) Failed to connect to 192.168.5.50 port 80: Connection refused
MYPC:~ user$ ping hda
PING hda.domain.com (192.168.5.50): 56 data bytes
64 bytes from 192.168.5.50: icmp_seq=0 ttl=64 time=2.399 ms
64 bytes from 192.168.5.50: icmp_seq=1 ttl=64 time=11.826 ms
64 bytes from 192.168.5.50: icmp_seq=2 ttl=64 time=1.966 ms
64 bytes from 192.168.5.50: icmp_seq=3 ttl=64 time=7.850 ms
64 bytes from 192.168.5.50: icmp_seq=4 ttl=64 time=22.066 ms
64 bytes from 192.168.5.50: icmp_seq=5 ttl=64 time=2.097 ms
64 bytes from 192.168.5.50: icmp_seq=6 ttl=64 time=4.634 ms
^C
--- hda.domain.com ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.966/7.548/22.066/6.814 ms
From Fedora terminal (root user):
- same result observed as from MYPC - I can ping hda, but curl for hda:80 is resulting in error "Connection refused"
Any firewall on Fedora is active by default installation I should be aware of?
UPDATE:
Tried "firewall-cmd --permanent --add-service=http"
I got result "FirewallD is not running".
Also tried to see netstat (netstat -tpln) - I didnt see any :80 there. Also went to check iptables (iptables -L -n -v) - nothing defined there.
Any help would be appreciated.
#3 Updated by bigfoot65 about 4 years ago
Check to ensure the web server is running:
sudo systemctl status httpd
If not, try to start it:
sudo systemctl start httpd
#4 Updated by visionnaire about 4 years ago
- Priority changed from Normal to High
Even after new installation (format, install Fedora 23 again, install Amahi again), I have outstanding issue described above.
See terminal info below:
[root@localhost ~]# sudo systemctl status httpd httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2017-02-12 17:06:58 CET; 16min ago Process: 971 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE) Main PID: 971 (code=exited, status=1/FAILURE) Feb 12 17:06:56 localhost.localdomain systemd[1]: Starting The Apache HTTP Server... Feb 12 17:06:58 localhost.localdomain httpd[971]: httpd: Syntax error on line 56 of /etc/httpd/c...ity Feb 12 17:06:58 localhost.localdomain systemd[1]: httpd.service: Main process exited, code=exite...URE Feb 12 17:06:58 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server. Feb 12 17:06:58 localhost.localdomain systemd[1]: httpd.service: Unit entered failed state. Feb 12 17:06:58 localhost.localdomain systemd[1]: httpd.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. [root@localhost ~]# sudo systemctl status httpd -l httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2017-02-12 17:06:58 CET; 16min ago Process: 971 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE) Main PID: 971 (code=exited, status=1/FAILURE) Feb 12 17:06:56 localhost.localdomain systemd[1]: Starting The Apache HTTP Server... Feb 12 17:06:58 localhost.localdomain httpd[971]: httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Syntax error on line 40 of /etc/httpd/conf.modules.d/00-base.conf: Cannot load modules/mod_http2.so into server: /etc/httpd/modules/mod_http2.so: undefined symbol: nghttp2_session_change_stream_priority Feb 12 17:06:58 localhost.localdomain systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE Feb 12 17:06:58 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server. Feb 12 17:06:58 localhost.localdomain systemd[1]: httpd.service: Unit entered failed state. Feb 12 17:06:58 localhost.localdomain systemd[1]: httpd.service: Failed with result 'exit-code'. [root@localhost ~]# curl hda curl: (6) Could not resolve host: hda [root@localhost ~]# curl localhost curl: (7) Failed to connect to localhost port 80: Connection refused [root@localhost ~]# sudo systemctl start httpd Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. [root@localhost ~]# journalctl -xe Feb 12 17:22:56 localhost.localdomain audit[1376]: USER_ACCT pid=1376 uid=0 auid=1000 ses=1 msg='op=PA Feb 12 17:22:56 localhost.localdomain su[1376]: (to root) visionnaire on pts/0 Feb 12 17:22:56 localhost.localdomain audit[1376]: CRED_ACQ pid=1376 uid=0 auid=1000 ses=1 msg='op=PAM Feb 12 17:22:56 localhost.localdomain su[1376]: pam_systemd(su-l:session): Cannot create session: Alre Feb 12 17:22:56 localhost.localdomain su[1376]: pam_unix(su-l:session): session opened for user root b Feb 12 17:22:56 localhost.localdomain audit[1376]: USER_START pid=1376 uid=0 auid=1000 ses=1 msg='op=P Feb 12 17:22:59 localhost.localdomain sudo[1398]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMA Feb 12 17:22:59 localhost.localdomain audit[1398]: USER_CMD pid=1398 uid=0 auid=1000 ses=1 msg='cwd="/ Feb 12 17:22:59 localhost.localdomain audit[1398]: CRED_REFR pid=1398 uid=0 auid=1000 ses=1 msg='op=PA Feb 12 17:22:59 localhost.localdomain sudo[1398]: pam_systemd(sudo:session): Cannot create session: Al Feb 12 17:22:59 localhost.localdomain sudo[1398]: pam_unix(sudo:session): session opened for user root Feb 12 17:22:59 localhost.localdomain audit[1398]: USER_START pid=1398 uid=0 auid=1000 ses=1 msg='op=P Feb 12 17:22:59 localhost.localdomain sudo[1398]: pam_unix(sudo:session): session closed for user root Feb 12 17:22:59 localhost.localdomain audit[1398]: USER_END pid=1398 uid=0 auid=1000 ses=1 msg='op=PAM Feb 12 17:22:59 localhost.localdomain audit[1398]: CRED_DISP pid=1398 uid=0 auid=1000 ses=1 msg='op=PA Feb 12 17:23:16 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=429496729 Feb 12 17:23:25 localhost.localdomain sudo[1404]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMA Feb 12 17:23:25 localhost.localdomain audit[1404]: USER_CMD pid=1404 uid=0 auid=1000 ses=1 msg='cwd="/ Feb 12 17:23:25 localhost.localdomain audit[1404]: CRED_REFR pid=1404 uid=0 auid=1000 ses=1 msg='op=PA Feb 12 17:23:25 localhost.localdomain sudo[1404]: pam_systemd(sudo:session): Cannot create session: Al Feb 12 17:23:25 localhost.localdomain sudo[1404]: pam_unix(sudo:session): session opened for user root Feb 12 17:23:25 localhost.localdomain audit[1404]: USER_START pid=1404 uid=0 auid=1000 ses=1 msg='op=P Feb 12 17:23:25 localhost.localdomain sudo[1404]: pam_unix(sudo:session): session closed for user root Feb 12 17:23:25 localhost.localdomain audit[1404]: USER_END pid=1404 uid=0 auid=1000 ses=1 msg='op=PAM Feb 12 17:23:25 localhost.localdomain audit[1404]: CRED_DISP pid=1404 uid=0 auid=1000 ses=1 msg='op=PA Feb 12 17:25:08 localhost.localdomain sudo[1415]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMA Feb 12 17:25:08 localhost.localdomain audit[1415]: USER_CMD pid=1415 uid=0 auid=1000 ses=1 msg='cwd="/ Feb 12 17:25:08 localhost.localdomain audit[1415]: CRED_REFR pid=1415 uid=0 auid=1000 ses=1 msg='op=PA Feb 12 17:25:08 localhost.localdomain sudo[1415]: pam_systemd(sudo:session): Cannot create session: Al Feb 12 17:25:08 localhost.localdomain sudo[1415]: pam_unix(sudo:session): session opened for user root Feb 12 17:25:08 localhost.localdomain audit[1415]: USER_START pid=1415 uid=0 auid=1000 ses=1 msg='op=P Feb 12 17:25:08 localhost.localdomain systemd[1]: Starting The Apache HTTP Server... -- Subject: Unit httpd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit httpd.service has begun starting up. Feb 12 17:25:08 localhost.localdomain httpd[1419]: httpd: Syntax error on line 56 of /etc/httpd/conf/h Feb 12 17:25:08 localhost.localdomain systemd[1]: httpd.service: Main process exited, code=exited, sta Feb 12 17:25:08 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server. -- Subject: Unit httpd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit httpd.service has failed. -- -- The result is failed. Feb 12 17:25:08 localhost.localdomain systemd[1]: httpd.service: Unit entered failed state. Feb 12 17:25:08 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=42949672 Feb 12 17:25:08 localhost.localdomain systemd[1]: httpd.service: Failed with result 'exit-code'. Feb 12 17:25:08 localhost.localdomain sudo[1415]: pam_unix(sudo:session): session closed for user root Feb 12 17:25:08 localhost.localdomain audit[1415]: USER_END pid=1415 uid=0 auid=1000 ses=1 msg='op=PAM Feb 12 17:25:08 localhost.localdomain audit[1415]: CRED_DISP pid=1415 uid=0 auid=1000 ses=1 msg='op=PA [root@localhost ~]#
#5 Updated by bigfoot65 about 4 years ago
- Priority changed from High to Normal
Try doing the following:
sudo dnf update
Then reboot.
Also provide the URL for:
apaste --sysinfo
#6 Updated by visionnaire about 4 years ago
Thanks, that did the job!
#7 Updated by cpg about 4 years ago
- Status changed from Assigned to Closed
- Assignee changed from cpg to bigfoot65
#8 Updated by bigfoot65 almost 4 years ago
- Subject changed from some times it takes an extra reboot to get networking right to Amahi 9/10 Sometimes it takes an extra reboot to get networking right
- Target version changed from amahi-9 to amahi-10
#9 Updated by cpg almost 4 years ago
- Subject changed from Amahi 9/10 Sometimes it takes an extra reboot to get networking right to Amahi 10 Sometimes it takes an extra reboot to get networking right
- Status changed from Closed to Assigned
- Assignee changed from bigfoot65 to cpg
Also available in: Atom