Hi all,
TL:DR: Did you ever see something like httpd is dead at Thu Nov 30 11:13:46 2017
App watch dog try to recover httpd at the 2 time
httpd is dead at Thu Nov 30 11:14:46 2017
---- more specific info
I've been trying to get to the web gui of my zywall the last few days but with no avail so I need your help :)
I know the way to start the gui from cli which I have console access to. I did so and the show status shows it's activated (both http and https) but I still can't access it from various browsers (Chrome, Safari, Firefox) all with cleaned caches and such. Also from windows and mac.
What I did:
-Full reset (30/30/30 rule) which worked and reset everything
-Applied different configuration files (some old ones from 2016 which I know work 100%)
-Upgraded firmware from 4.15 to 4.25 latest
There's a message I'm getting while logged in the cli, below:
look at lines 1-5, I have no idea why the httpd service fails and have no means to check it further with unix like tools.
XRouter> httpd is dead at Thu Nov 30 11:13:46 2017App watch dog try to recover httpd at the 2 timehttpd is dead at Thu Nov 30 11:14:46 2017App watch dog try to recover httpd at the 3 timehttpd is dead at Thu Nov 30 11:15:46 2017httpd is dead at Thu Nov 30 11:16:46 2017Recover httpd daemon fail.Ready to reboot system...Sleep 120 seconds to collect diagnostic-info ...Sleep 60 seconds to collect diagnostic-info ...Sleep 60 seconds to collect diagnostic-info ...Sleep 60 seconds to collect diagnostic-info ...Sleep 60 seconds to collect diagnostic-info ...diagnostic-info collect complete, reboot system now.% ZyWALL is going to reboot!link_updown daemon (PID:1676) was terminated by "sending PID:11119, UID:0" due to signal:15select: Interrupted system call Welcome to ZyWALL 110 Username:Terminate All Processes: OKkill_process_and_umountfs() returns -6reboot: Restarting system U-Boot 2011.03 (Development build, svnversion: u-boot:437M, exec:) (Build time: Jan 03 2014 - 16:00:13) BootModule Version: V1.09 | Jan 03 2014 16:00:13DRAM: Size = 1024 Mbytes Press any key to enter debug mode within 3 seconds.............................................................mount: wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so Start to check file system.../dev/sda3: 488/20480 files (0.6% non-contiguous), 69119/81920 blocks/dev/sda4: 142/23040 files (4.2% non-contiguous), 24883/92160 blocksDoneKernel Version: V3.10.20 | 2017-07-12 02:36:14ZLD Version: V4.25(AAAA.1) | 2017-07-13 10:36:33 INIT: version 2.86 bootingInitializing Debug Account Authentication Seed (DAAS)... done.Setting the System Clock using the Hardware Clock as reference...System Clock set. Local time: Thu Nov 30 11:23:43 UTC 2017 INIT: Entering runlevel: 3Insmod ZYKLOG Module. Starting zylog daemon: zylogd zylog starts.Starting syslog-ng secu-reporter.Starting ZLD Wrapper Daemon....Starting uam daemon.Starting myzyxel daemon.Starting periodic command scheduler: cron.Start ZyWALL system daemon....Starting link_updown daemon.Check signature packageCheck av signature packageADP version 3.05 loaded.............................................Applying system configuration file, please wait.........% Request certificate cannot be used as server certificate.........% Request certificate cannot be used as server certificate..........ZyWALL system is configured successfully with startup-config.conf Got LINK_CHANGEPort [4] Copper is up --> Group [4] is up
note: Other than that the zywall is working fine, routing and switching properly like before.
note 2: Other services like telnet work when enabling them.
note 3: I get no message when running ip http server and ip http secure-server
Any help is greatly appreciated and a ticket to zyxel is also raised. so fingers crossed :)
↧