Unsolved Upgrade fog 1.2.0 to the svn version 4499 Debian Wheezy, All service won't start.

[frenk]

Hello, I realized that none of the services FOG Démare on my server after it updates.

root@fogserver /etc/dhcp # /etc/init.d/FOGMulticastManager start
[ ok ] Starting FOG Computer Imaging Solution: FOGMulticastManager.
root@fogserver /etc/dhcp # /etc/init.d/FOGMulticastManager status
[FAIL] FOGMulticastManager is not running ... failed!
root@fogserver /etc/dhcp # /etc/init.d/FOGMulticastManager stop
[....] Stopping FOG Computer Imaging Solution: FOGMulticastManagerstart-stop-daemon: warning: failed to kill 9002: No such process
. ok
root@fogserver /etc/dhcp # /opt/fog/service/FOGMulticastManager/FOGMulticastManager
PHP Fatal error:  Call to a member function query() on null in /var/www/fog/lib/db/MySQL.class.php on line 63

And it is like for other services.
thanks for your help.

[Wayne Workman]

@frenk Can you verify that your storage node’s “interface” setting is set correctly?

Storage Management -> [your storage node] -> Interface

You can get a listing of the interfaces available with this command:

ip link show

For example, in the previous output you supplied, it would appear that the “eth0” interface is the one that should have been set for the PREVIOUS build.
Can you get us some logs for the multicast manager? they should be here:
FOG Configuration -> Log Viewer -> Multicast

[frenk]

Still same error.
https://forums.fogproject.org/topic/5688/upgrade-fog-1-2-0-to-the-svn-version-4499-debian-wheezy-all-service-won-t-start

[frenk]

Thank you for information.

I have no “storage node settings” but I “FOG Storage Nodes” to have I sent the Desktop taken previously, and has no interface parameter.
I found two or parameter may have configured the interface:
“FOG_UDPCAST_INTERFACE” and “FOG_NFS_ETH_MONITOR” while both configured.

Now I’m on debian 8 and Fog Version: 4511, every folder and file in “/ var / www / fog” and “/ opt / fog” are readable by everyone.
And my file system is not full.
It’s just that the service does not start, they cough the same mistake.

root@fogserver /etc/dhcp # systemctl restart FOGScheduler.service
root@fogserver /etc/dhcp # systemctl status FOGScheduler.service
● FOGScheduler.service - FOGScheduler
   Loaded: loaded (/lib/systemd/system/FOGScheduler.service; enabled)
   Active: failed (Result: exit-code) since ven. 2015-08-28 13:49:32 CEST; 12s ago
  Process: 11057 ExecStart=/opt/fog/service/FOGTaskScheduler/FOGTaskScheduler & (code=exited, status=255)
 Main PID: 11057 (code=exited, status=255)

août 28 13:49:32 fogserver FOGTaskScheduler[11057]: PHP Fatal error:  Call to a member function query() on null in /var/www/fog/lib/db/MySQL.class.php on line 63
août 28 13:49:32 fogserver systemd[1]: FOGScheduler.service: main process exited, code=exited, status=255/n/a
août 28 13:49:32 fogserver systemd[1]: Unit FOGScheduler.service entered failed state.
root@fogserver /etc/dhcp #  systemctl restart FOGMulticastManager.service
root@fogserver /etc/dhcp #  systemctl status FOGMulticastManager.service
● FOGMulticastManager.service - FOGMulticastManager
   Loaded: loaded (/lib/systemd/system/FOGMulticastManager.service; enabled)
   Active: failed (Result: exit-code) since ven. 2015-08-28 13:50:01 CEST; 8s ago
  Process: 11070 ExecStart=/opt/fog/service/FOGMulticastManager/FOGMulticastManager & (code=exited, status=255)
 Main PID: 11070 (code=exited, status=255)

août 28 13:50:01 fogserver FOGMulticastManager[11070]: PHP Fatal error:  Call to a member function query() on null in /var/www/fog/lib/db/MySQL.class.php on line 63
août 28 13:50:01 fogserver systemd[1]: FOGMulticastManager.service: main process exited, code=exited, status=255/n/a
août 28 13:50:01 fogserver systemd[1]: Unit FOGMulticastManager.service entered failed state.

If you have any idea I’m interested.
Thank you.

[Tom Elliott]

I’m confused. Is there any error’s as to why it’s not starting? Is something else failing to start? Is the file system full?

[Wayne Workman]

@frenk You’re not the only one - this revision has some minor issues but nothing that breaks primary functionality.

In your storage node settings, ensure that one of the two interfaces is set as the interface. It needs to be either eth0 or eth1

Also - you should try Debian 8. The very latest FOG Trunk revisions are tested on Debian 8. I cannot speak to the stability or functionality of current FOG Trunk on Debian 7.8.

Perhaps the @Developers could chime in on how current FOG Trunk works on 7.8.

Also - run the upgrade again - there’s been some changes in the last day or two that may or may not fix your issues. they are web directory permissions related problems that are specific to Ubuntu and therefore probably affect Debian.

[frenk]

I am the only one to have this problemmes with SVN version ?
Thank you.

[frenk]

 ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
    link/ether 84:2b:2b:1a:c6:53 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 84:2b:2b:1a:c6:55 brd ff:ff:ff:ff:ff:ff

I specify that I have the same problem on:
FOGImageReplicator
FOGScheduler
FOGSnapinReplicator

[Wayne Workman]

Can you give us the output of this command?

ip link show

And also a screen shot of your storage node settings too, please. Keep the password covered, we don’t need that.