Log files missing r5096 v6895
-
@Raymond-Bell /opt/fog/log is the same location as /var/log/fog (they’re just a link to one another.
Is it possible for you to try sudoing up to root (
sudo -i
) then try restarting the FOGImageReplicator? -
I did and still no files
-
Than you may have to touch the files first.
sudo touch /opt/fog/log/{mulicast,fogsnaprep,fogscheduler,fogreplicator,pinghosts}.log sudo service FOGImageReplicator restart sudo service FOGScheduler restart sudo service FOGSnapinReplicator restart sudo service FOGPingHosts restart sudo service FOGMulticastManager restart
-
That worked. I can see the files now on the master node…
Do i need to do this on slave node?
-
-
@Raymond-Bell Do they actually have data though?
-
NO no data and still IP error
-
what version are you currently running?
-
What I mean by data (not that you don’t know how or anything), but if you run
cat /opt/fog/log/fogreplicator.log
is there anything output? -
@Tom-Elliott
r5102 v6907root@fog-GX620-K2:~# cat /opt/fog/log/fogreplicator.log root@fog-GX620-K2:~#
-
@Tom-Elliott
the ownership of the files are set to root also i see do i need to change that to owner fog? -
@Raymond-Bell You can try it, but I doubt it will work.
Do you have /var/www/fog and /var/www/html/fog?
-
fog@fog-GX620-K2:~$ cd /var/www/fog fog@fog-GX620-K2:/var/www/fog$ ls client favicon.ico fogdoc lib mobile status commons fog index.php management service fog@fog-GX620-K2:/var/www/fog$ cd fog@fog-GX620-K2:~$ cd /var/www/html/fog fog@fog-GX620-K2:/var/www/html/fog$ ls client favicon.ico fogdoc lib mobile status commons fog index.php management service fog@fog-GX620-K2:/var/www/html/fog$
-
-
fog@fog-GX620-K2:~$ sudo ls -l /var/www total 4 lrwxrwxrwx 1 root root 17 Mar 2 20:02 fog -> /var/www/html/fog drwxr-xr-x 3 root root 4096 Mar 22 08:26 html fog@fog-GX620-K2:~$ sudo ls -l /var/www/html/ total 20 drwxr-xr-x 10 www-data www-data 4096 Mar 22 08:26 fog -rw-r--r-- 1 root root 11510 Mar 2 11:25 index.html -rw-r--r-- 1 root root 45 Mar 2 11:27 index.php fog@fog-GX620-K2:~$
-
@Raymond-Bell Is this still an issue in latest trunk?