OK, I fixed the Apache/HTTPD issue. After much, much, much searching I found this site for a fix and it worked for me.
http://awsadminz.com/httpd-service-main-process-exited-kill-cannot-find-process/
Should I post a separate tutorial as a fix for this issue?
As for the kernel thing, I tried a different PC and it is working fine. I guess I’ll have to figure that one out.
Posts
-
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
-
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
File system still seems fine:
Filesystem Type Inodes IUsed IFree IUse% Size Used Avail Use% File Mounted on /dev/mapper/centos00-root00 ext4 1.3M 164K 1.1M 13% 20G 7.7G 11G 42% - / devtmpfs devtmpfs 470K 494 469K 1% 1.9G 0 1.9G 0% - /dev tmpfs tmpfs 473K 10 473K 1% 1.9G 5.3M 1.9G 1% - /dev/shm tmpfs tmpfs 473K 645 473K 1% 1.9G 17M 1.9G 1% - /run tmpfs tmpfs 473K 13 473K 1% 1.9G 0 1.9G 0% - /sys/fs/cgroup /dev/sda5 ext4 63K 365 63K 1% 969M 329M 574M 37% - /boot /dev/mapper/fog-opt_fog_images ext4 26M 10K 26M 1% 395G 80G 295G 22% - /opt /dev/sdb1 ext4 261M 15 261M 1% 8.1T 91M 7.7T 1% - /images tmpfs tmpfs 473K 30 473K 1% 379M 16K 379M 1% - /run/user/1000 -
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
I believe httpd is the problem right now. I tried to go into FOG management and got an "Unable to connect"page. So I tried to run the installer and apache2 failed to start. I’ve looked at a lot of sites with this similar issue and cannot determine a solution for me. I’ve started, restarted, stopped, reloaded, kill, and tried to update apache/httpd. Here is some info that I hope can help.
[root@localhost httpd]# service httpd start Redirecting to /bin/systemctl start httpd.service 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 httpd]# systemctl status httpd.service ● httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2016-12-01 15:08:00 CST; 30s ago Docs: man:httpd(8) man:apachectl(8) Process: 13974 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE) Process: 13959 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE) Main PID: 13959 (code=exited, status=1/FAILURE) Dec 01 15:08:00 localhost.localdomain systemd[1]: Starting The Apache HTTP Server... Dec 01 15:08:00 localhost.localdomain httpd[13959]: AH00558: httpd: Could not reliably determine the server's fully qu...ssage Dec 01 15:08:00 localhost.localdomain systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE Dec 01 15:08:00 localhost.localdomain kill[13974]: kill: cannot find process "" Dec 01 15:08:00 localhost.localdomain systemd[1]: httpd.service: control process exited, code=exited status=1 Dec 01 15:08:00 localhost.localdomain systemd[1]: Failed to start The Apache HTTP Server. Dec 01 15:08:00 localhost.localdomain systemd[1]: Unit httpd.service entered failed state. Dec 01 15:08:00 localhost.localdomain systemd[1]: httpd.service failed. Hint: Some lines were ellipsized, use -l to show in full. [root@localhost httpd]# journalctl -xn -- Logs begin at Wed 2016-11-30 13:17:57 CST, end at Thu 2016-12-01 15:08:31 CST. -- Dec 01 15:08:00 localhost.localdomain kill[13974]: kill: cannot find process "" Dec 01 15:08:00 localhost.localdomain systemd[1]: httpd.service: control process exited, code=exited status=1 Dec 01 15:08:00 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. Dec 01 15:08:00 localhost.localdomain systemd[1]: Unit httpd.service entered failed state. Dec 01 15:08:00 localhost.localdomain systemd[1]: httpd.service failed. Dec 01 15:08:01 localhost.localdomain dhcpd[2890]: DHCPDISCOVER from 36:02:86:28:b1:8b (MCWPL53) via enp30s0 Dec 01 15:08:01 localhost.localdomain dhcpd[2890]: DHCPOFFER on 10.10.0.10 to 36:02:86:28:b1:8b (MCWPL53) via enp30s0 Dec 01 15:08:01 localhost.localdomain polkitd[777]: Unregistered Authentication Agent for unix-process:13944:9300666 (system b Dec 01 15:08:28 localhost.localdomain dhcpd[2890]: DHCPINFORM from 10.10.1.167 via enp30s0: not authoritative for subnet 10.10 Dec 01 15:08:31 localhost.localdomain dhcpd[2890]: DHCPINFORM from 10.10.1.130 via enp30s0: not authoritative for subnet 10.10I just don’t understand it enough to completely know what I’m looking at.
-
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
I started thinking the same thing. I’m going to try a different PC and see what happens.
-
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
Well, that didn’t work. The cable is fine. I get internet and I can ping it.
-
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
@Tom-Elliott
I just tried it cause I went to https://ipxe.org/0f0a6039, from the screen shot, and that was one of the suggestions.
I’ll try that and see… -
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
Not sure if this was the right thing to try but I ran:
git clone git://git.ipxe.org/ipxe.gitAnd it ended with this:
[AR] bin/blib.a ar: creating bin/blib.a [HOSTCC] util/zbin util/zbin.c:7:18: fatal error: lzma.h: No such file or directory #include <lzma.h> ^ compilation terminated. make: *** [util/zbin] Error 1 -
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
@ManofValor
By the way, this screen is consistent now. -
RE: Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
@Tom-Elliott
So I checked the partition size’s:[root@localhost fogadmin]# df -h --o Filesystem Type Inodes IUsed IFree IUse% Size Used Avail Use% File Mounted on /dev/mapper/centos00-root00 ext4 1.3M 158K 1.1M 13% 20G 7.5G 12G 41% - / devtmpfs devtmpfs 470K 494 469K 1% 1.9G 0 1.9G 0% - /dev tmpfs tmpfs 473K 9 473K 1% 1.9G 4.5M 1.9G 1% - /dev/shm tmpfs tmpfs 473K 643 473K 1% 1.9G 8.9M 1.9G 1% - /run tmpfs tmpfs 473K 13 473K 1% 1.9G 0 1.9G 0% - /sys/fs/cgroup /dev/sda5 ext4 63K 365 63K 1% 969M 329M 574M 37% - /boot /dev/mapper/fog-opt_fog_images ext4 26M 10K 26M 1% 395G 80G 295G 22% - /opt /dev/sdb1 ext4 261M 15 261M 1% 8.1T 91M 7.7T 1% - /images tmpfs tmpfs 473K 29 473K 1% 379M 12K 379M 1% - /run/user/1000I re-seated the memory and now I’m getting this new screen:
Should I start a new post for this one?
-
Kernal panic - not syncing: Attempted to kill init!posted in FOG Problems
Server
- FOG Version: 1.3.0-RC-26
- OS: Centos 7
Client
- Service Version:
- OS: Win 7
Description
So I go to check on my FOG server, cause it’s been a while, and, after updating everything, I run an image on a test machine to make sure it’s still working. I get Different screens each time I reboot. See below examples.
Haven’t been able to find anything that helps me on the forum or net.
-
RE: CentOS 6 GUI login loop.posted in Linux Problems
@Tom-Elliott
Ok, this thread is solved. After I deleted everything I was able to login. Thanks again guys. -
RE: CentOS 6 GUI login loop.posted in Linux Problems
@Wayne-Workman
Good morning,
Everything on the NAS is just tests, so if I don’t care what’s deleted then I don’t need to unmount, right? -
RE: CentOS 6 GUI login loop.posted in Linux Problems
I ran this:
[root@localhost Downloads]# df -ah --o Filesystem Type Inodes IUsed IFree IUse% Size Used Avail Use% File Mounted on rootfs - - - - - - - - - - / sysfs sysfs 0 0 0 - 0 0 0 - - /sys proc proc 0 0 0 - 0 0 0 - - /proc devtmpfs devtmpfs 470K 494 469K 1% 1.9G 0 1.9G 0% - /dev securityfs securityfs 0 0 0 - 0 0 0 - - /sys/kernel/security tmpfs tmpfs 473K 6 473K 1% 1.9G 2.8M 1.9G 1% - /dev/shm devpts devpts 0 0 0 - 0 0 0 - - /dev/pts tmpfs tmpfs 473K 658 473K 1% 1.9G 8.9M 1.9G 1% - /run tmpfs tmpfs 473K 13 473K 1% 1.9G 0 1.9G 0% - /sys/fs/cgroup cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/systemd pstore pstore 0 0 0 - 0 0 0 - - /sys/fs/pstore cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/cpu,cpuacct cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/net_cls cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/blkio cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/hugetlb cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/perf_event cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/devices cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/memory cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/cpuset cgroup cgroup 0 0 0 - 0 0 0 - - /sys/fs/cgroup/freezer configfs configfs 0 0 0 - 0 0 0 - - /sys/kernel/config /dev/mapper/centos00-root00 ext4 1.3M 155K 1.2M 13% 20G 20G 0 100% - / systemd-1 - - - - - - - - - - /proc/sys/fs/binfmt_misc mqueue mqueue 0 0 0 - 0 0 0 - - /dev/mqueue debugfs debugfs 0 0 0 - 0 0 0 - - /sys/kernel/debug hugetlbfs hugetlbfs 0 0 0 - 0 0 0 - - /dev/hugepages sunrpc rpc_pipefs 0 0 0 - 0 0 0 - - /var/lib/nfs/rpc_pipefs nfsd nfsd 0 0 0 - 0 0 0 - - /proc/fs/nfsd /dev/sda5 ext4 63K 365 63K 1% 969M 329M 574M 37% - /boot /dev/mapper/fog-opt_fog_images ext4 26M 9.7K 26M 1% 395G 223G 152G 60% - /opt /dev/sdb1 ext4 261M 29 261M 1% 8.1T 52G 7.7T 1% - /opt/fog/images /dev/sdb1 ext4 261M 29 261M 1% 8.1T 52G 7.7T 1% - /images tmpfs tmpfs 473K 14 473K 1% 379M 12K 379M 1% - /run/user/42 gvfsd-fuse fuse.gvfsd-fuse 0 0 0 - 0.0K 0.0K 0.0K - - /run/user/42/gvfs fusectl fusectl 0 0 0 - 0 0 0 - - /sys/fs/fuse/connections tmpfs tmpfs 473K 1 473K 1% 379M 0 379M 0% - /run/user/1000 binfmt_misc binfmt_misc 0 0 0 - 0 0 0 - - /proc/sys/fs/binfmt_miscWhat does it all mean and how do I know what to delete or rearrange?
How did it fill up when I didn’t do anything? -
RE: CentOS 6 GUI login loop.posted in Linux Problems
@Wayne-Workman
I don’t understand, I haven’t put anything on there to fill it up? -
RE: CentOS 6 GUI login loop.posted in Linux Problems
@Wayne-Workman
So I can’t login cause it’s full? -
RE: CentOS 6 GUI login loop.posted in Linux Problems
I think turning the NAS back on will have fixed the disk space issue cause I haven’t done but a couple images since I got it going. Here is the df output.
[root@localhost fogadmin]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/centos00-root00 20535120 20389424 0 100% / devtmpfs 1921780 0 1921780 0% /dev tmpfs 1936948 2820 1934128 1% /dev/shm tmpfs 1936948 9076 1927872 1% /run tmpfs 1936948 0 1936948 0% /sys/fs/cgroup /dev/sda5 991512 336764 587164 37% /boot /dev/mapper/fog-opt_fog_images 413199680 233741596 158445604 60% /opt /dev/sdb1 8674999312 54524064 8183255204 1% /images tmpfs 387392 12 387380 1% /run/user/42 tmpfs -
RE: CentOS 6 GUI login loop.posted in Linux Problems
@Wayne-Workman
I can do that. Everything seems normal from the command line. -
CentOS 6 GUI login loop.posted in Linux Problems
Hey guys,
I cannot login to my FOG server. I get to the login screen and i type in my password and it acts like its logging in but just goes back to login screen. The other day I went to check on the FOG server, cause I haven’t used it in a few months, and I couldn’t get anything on my monitor. Everything was hooked up as I had not touch it since I had everything working the last time I used it. I did a hard reboot and it came up, but had some error that was too quick to take a pic of. I rebooted again to a previously good date and it worked fine. I logged in and updated everything without a hitch. I started a test image, just to make sure all was good, and in the middle of capturing this happened.
I looked over at my server and saw this.
Come to find out my NAS was powered down for some reason. So I turned it back on, rebooted my server and that’s when I got the login loop.
Hope this info helps. Let me know if you need any more info. Thanks.