Tasks not being processed

[Drevonovic]

Hello,

This is one of my first posts on this forum and I’m new to the FOG project.

After setting up a fog server 1.2.0 on an Ubuntu 14.04 LTS (Virtual) I was able to let my other laptop, which I use as a test device, connect to my server and display the menu.

When I issued the upload task in the web interface, the task goes to “active tasks” but is never processed. The laptop where the image needs to be uploaded from (the test device) never gets the task and jumps straight to the iPXE menu.

I’ve researched this forum for a solution but the only “fix” I found was a clean install, which I did several times already. So could anyone help me with this problem without a reinstall?

Thanks!

P.S. my test device gets the message “Host is NOT registered!” message, while both in the web interface as in the full host registration, the device is registered

[Sebastian Roth]

Registration, tasks and all the rest is assigned/related via MAC address. So please compare the clients MAC address with the one you see in the web interface in the hosts entry.

PS: You only need to to register the host once. Either on the web interface or via PXE menu (full host registration).

[Tom Elliott]

Can you get us a copy of both the error and access logs? The access log will show what url is passing which should indicate what is actually being sent to the server for checking if the host is registered or not.

[Drevonovic]

@Tom-Elliott I’m sorry for the delayed answer.
I have looked for the error and access logs before I posted this, but the problem here is that I cannot find any file having the logs in it :s

[Drevonovic]

@Uncle-Frank The MAC-addresses are correct. When I do a full registration for a second time (since it still says host is not registered), it does tell me he is already registered. It is the header of the iPXE menu that isn’t changing and I cannot find why it doesn’t change. As posted in my other answer to Tom Elliott, I can’t find any log files to check what is going wrong

[Sebastian Roth]

Ubuntu has the log files in /var/log/apache2/error.log and /var/log/apache2/access.log

sudo tail -f /var/log/apache2/error.log /var/log/apache2/access.log

[Drevonovic]

@Uncle-Frank Thanks!
@Tom-Elliott

[Wayne Workman]

@Drevonovic

What is the output of this?

ls -la /var/log/apache2/error.log

[Drevonovic]

@Wayne-Workman -rw-r----- 1 root adm 6935 okt 26 11;57 /var/log/apache2/error.log

[Wayne Workman]

@Drevonovic see how it has double forward slashes in the path below?

/opt/fog//log/multicast.log and /opt/fog//log/fogscheduler.log that can’t be right…

[Drevonovic]

@Wayne-Workman how can I change this? (I’m really new at this so sorry if this is a weird question)

[Wayne Workman]

@Drevonovic I’m not exactly sure, I haven’t seen that sort of issue before.

But, coming back to your registration issue, have you tried to delete the host from the DB and then re-register it?

When you select the host in the Web UI, towards the left at the bottom there should be a link for deleting.

[Drevonovic]

This is the only link I can find to delete my host in the host list. Don’t think it is this you meant?

[Drevonovic]

@Wayne-Workman Also, I cannot manage to find these 2 log files. /opt seems to have a map log in it, but don’t have any content :s

[Wayne Workman]

@Drevonovic I think that little remove link would work just fine. 1.2.0 looks worlds different than the current developmental version. So just delete that host and try to re-register it.

Here’s the delete link I was talking about:

[Drevonovic]

@Wayne-Workman In that case, yes I already tried that. It let me register the host again, it comes up in both the WEB UI as in the fog server, but the header of the menu isn’t changing

[Wayne Workman]

Is the host virtual or physical?

[Drevonovic]

@Wayne-Workman The host is physical, the server is virtual

[Sebastian Roth]

@Drevonovic The best I can offer now is to take a look at a packet dump. Capture packets while the client in question boots up so we can exactly see which request is send and which answer is generated.
For that please open two terminals on your server. Make sure that most of your browser windows and clients are closed/shutdown so that we don’t have too much other stuff interfering and filling the logs. In the install and run tcpdump:

sudo apt-get install tcpdump
sudo tcpdump -i eth0 -w bootmenu.pcap

Leave that and open the apache log in the second window:

sudo tail -f /var/log/apache2/error.log

Hit Enter twice or so that you see where it started last. Now boot up the client til you see the menu. Stop both commands with Ctrl+c and upload the PCAP file as well as the lines you see in the error.log (copy&paste).

[Drevonovic]

@Uncle-Frank I will do this the first thing tomorrow. I don’t have my environment available today which makes it hard to test this Let’s hope we can find something tomorrow