Postby ratrat4563 » Mon Apr 17, 2017 3:29 pm
I could not get any response after loading Amahi per the instructions following the reboot. I had used a copy of Seagate Disk Wizard to take the hard drive back to a clean condition to ensure that there was nothing on the disk which would cause the problem (I had four disks and no matter which one I used I could not get my network to connect with the HDA) My browser would not connect to Amahi and when I went to the computer it was installed on this is the screen display (my inputs are in bold, Amahi response in italic).
sudo systemctl status httpd
httpd.service – The Apache HTTP Server
Loaded: loaded (/user/lib/system/system/httpd.services: enabl3ed: vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-04-17 08:20:14 PDT: 30s ago
Process: 748 ExecStart=user/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE
Main PID: 748 (code=exited, status=1/FAILURE)
Apr 17 08:20:13 localhost.localdomain systemcmd[1]: Starting The Apache HTTP Server…
Apr 17 08:20:14 localhost.localdomain httpd[740]: httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Syntax e…ority
Apr 17 08:20:14 localhost.localdomain system[1]: httpd.service: Main process exited, code exited, status=11/FAILURE.
Apr 17 08:20:14 localhost.localdomain system[1]: Failed to start The Apache HTTP Server.
Apr 17 08:20:14 localhost.localdomain system[1]: httpd.service: Unit entered failed state.
Apr 17 08:20:14 localhost.localdomain system[1]: httpd.service: Failed with result ‘exit-code’.
I next tried starting the stem with the sudo systemctl start httpd command without success. I next used the command sudo ddnf update. After the update completed and I performed a reboot of the system I observed operation of the system per the Amahi wiki.
Wanting to fully understand where the problem lied I used the Seagate Disc Wizard to return the hard drive to a new condition with a partition on 20 GB and formatted in EXT4. With the drive in a bare condition I loaded Fedora 23 (had downloaded in the last two weeks from the primary netinstall link on the Amahi install wiki page). After installation of Fedora 23 and rebooting the system I proceeded to install Amahi 9 per the Install Amahi 9 instructions on the wiki. Upon completion of the install I was asked if I wanted to reboot and typed yes. The system rebooted and instead of going to another computer I logged on and then input sudo systemctl status httpd and received the same response as above. After inputting the sudo ddnf update command and the system performing an update followed by a reboot the system worked correctly.
Having spent over 35 years working on Fire Control Radars (hardware, not the software side) I can only deduce that when a clean load is installed on a clean system and an error is received that the code has an error which is corrected by the code loaded during the update command. I have seen where just 1 incorrect bit has resulted in total system failure to the Weapons System and feel the there is probably something wrong with the software and hope that this will help in its location and repair.