Ubuntu Server 19.10, Failed to stop web service

Sebastian Roth

@Skeer Welcome to the forums! The latest official FOG release came out before Ubuntu 19.10 was even released and so it’s got a bit of an issue. We have been working a lot on the next release 1.5.8 that will come out soon. If you don’t want to wait you can also use one of the development versions as mentioned by Fog_Newb. Though I might add to this that there are two different ones:

dev-branch is where we work on right now to be released as 1.5.8 soon
working-1.6 is the dev version of what we also work on to come out as FOG 1.6 some time in the future (no date yet).

You are welcome to try out one or the other but be aware the 1.6 dev version is under heavy development and there is no easy way back to the 1.5.x versions as of now.

...
fogadmin@ssi-fog:~/git/fogproject/bin$ sudo ./installfog.sh
...

We don’t recommend running the installer using sudo anymore. I have just updated information on the website. While it works in most cases we have seen things going wrong that way as well. Better use:

sudo -i
cd fogproject..../bin
./installfog.sh

Skeer

Thanks Guys! I’ll def be giving 1.6 a try. This is a new test server and has nothing else on it… if I need to nuke it to start over so be it.

Skeer

@Skeer said in Ubuntu Server 19.10, Failed to stop web service:

Thanks Guys! I’ll def be giving 1.6 a try. This is a new test server and has nothing else on it… if I need to nuke it to start over so be it.

So the dev-branch installed like a champ, I can pull up and login to the web gui. Except some process must not be running, nmap shows no port 69 listening.
Test clients fail to pxt boot claiming a tftp timeout.

Skeer

@Skeer said in Ubuntu Server 19.10, Failed to stop web service:

@Skeer said in Ubuntu Server 19.10, Failed to stop web service:

Thanks Guys! I’ll def be giving 1.6 a try. This is a new test server and has nothing else on it… if I need to nuke it to start over so be it.

So the dev-branch installed like a champ, I can pull up and login to the web gui. Except some process must not be running, nmap shows no port 69 listening.
Test clients fail to pxt boot claiming a tftp timeout.

Went ahead and rebooted… journalctl only shows issues with FogSnapinReplicator starting and stopping ever second.

Sebastian Roth

@Skeer Can you please post the two logs you find in the subdirectory error_logs (within fogproject/bin/ where you ran the installer)?

As well please run the following commands and post output here:

ps ax | grep tftp
systemctl status xinetd

Skeer

fogadmin@ssi-fog:~$ ps ax | grep tftp
  965 ?        Ss     0:00 /usr/sbin/in.tftpd --listen --user root --address :69 -s /tftpboot
25260 pts/0    S+     0:00 grep --color=auto tftp
fogadmin@ssi-fog:~$ systemctl status xinetd
● xinetd.service - LSB: Starts or stops the xinetd daemon.
   Loaded: loaded (/etc/init.d/xinetd; generated)
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)

Logs attached.fog_error.log foginstall.log

Sebastian Roth

@Skeer TFTP daemon seems to be running. The second command I had wrong from the top of my head. Run systemctl status tftpd-hpa instead. Should show it running.

Possibly you have a firewall enabled? Run those two commands as root and post output here:

iptables -L -n -v
ufw status

Skeer

Thanks for the continued help Sabastian.

No, iptables is not configured on this machine:

sudo iptables -L -n -v
[sudo] password for fogadmin:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
fogadmin@ssi-fog:~/git/fogproject-dev-branch/bin/error_logs$

Admittedly yesterday and previous our DHCP functions were handled at the firewall level. I had thought maybe there was some issue with that and since I’ve been meaning to do this anyway… last night I moved those functions to my domain controller (Server 2016). So the DHCP Options are configures correctly except a test PXE boot on a laptop behind me failed. It’s an HP so I didn’t get much feedback so I’m not sure the exact cause at this time.

Skeer

Am I correct in assuming that I should be able to see port 69 open via NMAP?

george1421

@Skeer On the fog server if you run netstat -an|grep :69
it should reply with a line that looks like this:

udp        0      0 0.0.0.0:69              0.0.0.0:*

I’m not familiar with ubuntu 19, but I would check in the /etc directory to see if there are files like hosts.allow and hosts.deny. The service name in.tftp kind of tells me they use the security wrapper around tftp to state who can connect to that service.

ref: https://www.poftut.com/linux-hosts-allow-hosts-deny-control-network-access/

Skeer

Ah I do see the port listed this way… a vanilla ‘netstat | less’ did not show :69 anywhere. Hence my confusion.

Ok so I was able to successfully PXE boot to a KVM guest, just not on a physical one yet.

So I know FOG works which is great!

Now I need to explore the settings and figure out how to successfully pull an image. Thanks for the help!

Skeer

Well this is disappointing. So due to an unrelated issue I decided to flatten this guest and build anew. I figured it’d be good since now I know the right version to use.
So flattened, new 19.10 install and the Apache service is still an issue. Even with installing the dev branch.
Manually installed php7.3, apache2, libmodule-apache, etc… not a thing I do now alleviates the failed to restart web services error.

Sebastian Roth

@Skeer said in Ubuntu Server 19.10, Failed to stop web service:

Manually installed php7.3, apache2, libmodule-apache, etc…

There shouldn’t be a need to manually install any packages. The installer should handle all that. We need more information on what exactly you’ve done and the error message you got to be able to help.

Skeer

@Sebastian-Roth Oh it’s exactly as described and exactly what happened the first go-round.
Since it’s in a failed state… let me do this. I’ll re-re-flatten the guest and start over. Fresh 19.10 install, ‘apt update/upgrade’ then I’ll run the fog installer from the dev-branch and see what happens.

Sebastian Roth

@Skeer said in Ubuntu Server 19.10, Failed to stop web service:

I’ll re-re-flatten the guest and start over.

Please use snapshots which are a perfect tool for those kind of tests. No need to reinstall from scratch all the time.

Sebastian Roth

@Skeer I just did a clean install on Ubuntu 19.10 using dev-branch and it worked perfectly fine. Haven’t done extensive testing beyond that but I would imagine it to capture and deploy images fine too.

Skeer

@Sebastian-Roth Keep forgetting about Snapshots… thats what I get for being in a hurry.

Ok so I’ve got an updated OS and following the steps here: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG I’ve pulled the dev-branch. So I should be good for the install script yes? (I’m not super experienced with git so I’m not feeling positive I actually have the full dev-branch source)

Sebastian Roth

@Skeer On the right track with the stuff you find in the wiki. The important command after cloning (downloading) the FOG repo is to switch to the dev-branch: git checkout dev-branch

By the way. If you want to wait a few more hours, FOG 1.5.8 will be out.

Skeer

I did checkout the dev-branch… but yeah sure I’ll be your huckleberry… err guinea pig.

For reference: https://www.youtube.com/watch?v=R8OWNspU_yE

Sebastian Roth

@Skeer FOG 1.5.8 is out now: https://github.com/FOGProject/fogproject/releases/tag/1.5.8

Ubuntu Server 19.10, Failed to stop web service

155

12.1k

17.3k

155.3k