Hostname Changer failed

[plegrand]

Server

• FOG Version: 1.3.4
• OS:

Client

• Service Version: 0.9.12
• OS:

Description

Once deploy task finished, hostname changer failed with this error message :

13/02/2017 15:20 Client-Info Version: 0.9.12
 13/02/2017 15:20 HostnameChanger Running...
 13/02/2017 15:20 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:21:85:71:BD:8E||00:00:00:00:00:00:00:E0&newService=1
 13/02/2017 15:20 Middleware::Communication Unknown Response: {"error":"ng"}

Does someone could help me ?

[plegrand]

@Jaymes-Driver
It’s already the best !!! ;-)

[Jaymes Driver]

@plegrand Hey no problem!

Thanks for reporting the issues you find. It helps to make FOG better!

[plegrand]

@Jaymes-Driver
Yes everything works fine, it’s just as you said a very minor issue.
It was for information only.
Thanks for your help

[Jaymes Driver]

@plegrand Did the task start? If so this might be a minor issue, and I sure Tom will fix it :)

I was hoping nothing was broken :P

[plegrand]

@Jaymes-Driver
Yes

[Jaymes Driver]

@plegrand looks like it listed the word “array” instead of the array of machines that are suppose to be there, if you go to the tasks page, do you see the task and your machine name?

[plegrand]

@Jaymes-Driver
Just for information, may be i should start an other thread but when i launch a deploy task for a group I’ve got this message :

Note “Array”
Is it normal ?

[Jaymes Driver]

@plegrand Thank you for providing the solution that you have found, I am certain that someone else will benefit from this information!

Glad you got it all sorted!

[plegrand]

The problem was the client version. (old version: 0.9.12)
I had to install the new one on each computer (0.11.9), then reboot each computer.
Then “reset encrypted data” on the group
Now it works fine.
I thought that once there was a new version on the server the client updated “alone”.

[plegrand]

@Tom-Elliott

In fact, pc are well renamed but not put into samba domain

14/02/2017 06:58 Bus Registering ParseBus in channel Power
14/02/2017 06:58 Bus Became bus client
14/02/2017 06:58 Bus Registering OnNotification in channel Notification
14/02/2017 06:58 Bus Registering OnUpdate in channel Update

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
14/02/2017 06:59 Client-Info Version: 0.9.12
14/02/2017 06:59 ClientUpdater Running...
14/02/2017 06:59 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=00:21:85:71:BD:8B||00:00:00:00:00:00:00:E0&newService=1
14/02/2017 06:59 Middleware::Communication Unknown Response: {"error":"null"}
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
14/02/2017 06:59 Client-Info Version: 0.9.12
14/02/2017 06:59 TaskReboot Running...
14/02/2017 06:59 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=taskreboot&mac=00:21:85:71:BD:8B||00:00:00:00:00:00:00:E0&newService=1
14/02/2017 06:59 Middleware::Communication Unknown Response: {"error":"null"}
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
14/02/2017 06:59 Client-Info Version: 0.9.12
14/02/2017 06:59 HostnameChanger Running...
14/02/2017 06:59 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:21:85:71:BD:8B||00:00:00:00:00:00:00:E0&newService=1
14/02/2017 06:59 Middleware::Communication Unknown Response: {"error":"null"}
------------------------------------------------------------------------------


------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
14/02/2017 06:59 Client-Info Version: 0.9.12
14/02/2017 06:59 SnapinClient Running...
14/02/2017 06:59 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=snapinclient&mac=00:21:85:71:BD:8B||00:00:00:00:00:00:00:E0&newService=1
14/02/2017 06:59 Middleware::Communication Unknown Response: {"error":"null"}
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
14/02/2017 06:59 Client-Info Version: 0.9.12
14/02/2017 06:59 PrinterManager Running...
14/02/2017 06:59 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=printermanager&mac=00:21:85:71:BD:8B||00:00:00:00:00:00:00:E0&newService=1
14/02/2017 06:59 Middleware::Communication Unknown Response: {"error":"null"}
------------------------------------------------------------------------------


------------------------------------------------------------------------------
-----------------------------------GreenFOG-----------------------------------
------------------------------------------------------------------------------
14/02/2017 06:59 Client-Info Version: 0.9.12
14/02/2017 06:59 GreenFOG Running...
14/02/2017 06:59 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=greenfog&mac=00:21:85:71:BD:8B||00:00:00:00:00:00:00:E0&newService=1
14/02/2017 06:59 Middleware::Communication Unknown Response: {"error":"null"}
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
14/02/2017 06:59 Client-Info Version: 0.9.12
14/02/2017 06:59 UserTracker Running...
14/02/2017 06:59 Middleware::Communication URL: http://192.168.39.243/fog/service/servicemodule-active.php?moduleid=usertracker&mac=00:21:85:71:BD:8B||00:00:00:00:00:00:00:E0&newService=1
14/02/2017 06:59 Middleware::Communication Unknown Response: {"error":"null"}
------------------------------------------------------------------------------

14/02/2017 06:59 Middleware::Communication URL: http://192.168.39.243/fog/management/index.php?node=client&sub=configure&newService=1
14/02/2017 06:59 Middleware::Communication Response: Success
14/02/2017 06:59 Service Sleeping for 78 seconds

[Tom Elliott]

Can you post the whole log?

[plegrand]

@Tom-Elliott
Then i upgraded.
Mon Feb 13, 2017 17:06 pm
Running Version 1.3.5-RC-5
SVN Revision: 6066

But now i’ve got this error : {“error”:“null”}

[Tom Elliott]

@plegrand That link already has all the information.

For initial pull you need the clone.

After that you do not need to continually clone or checkout.

When you need to update you would:

cd /home/svn/fogproject
git checkout dev-branch
git pull
cd bin
./installfog.sh -y

The -y will run the update without your input (no need to go to update db or anything.)

If you are already on the dev-branch, then you don’t need the git checkout dev-branch portion.

[plegrand]

@Tom-Elliott
last question … :-(

now, each time i want to upgrade i have to use this commands :

git clone https://github.com/FOGProject/fogproject.git /home/svn/fogproject
cd /home/svn/fogproject
git checkout dev-branch
cd bin
./installfog.sh

Thanks again for your help

[Tom Elliott]

Also, it can be used for “official” releases as well so yes. A single point.

[Tom Elliott]

@plegrand To install the RC’s yes.

[plegrand]

@Tom-Elliott
OK then now i have to only use git ?

Thanks

[Tom Elliott]

@plegrand Using git is what we are moving to.

SVN will only be used for the 1.3.X series and in particular (after 1.3.0) will only be used for “official” releases.

GIT will also have the “official” releases under the master branch. dev-branch will be the RC’s, and working-X.X.X will be the “trunk” items if you will (bleeding edge).

Tracking things are much easier under git than they were under SVN which is part of why we’re moving to GIT to begin with. SVN had capabilities but was very difficult. GIT also allows users to fork the repository and make pull requests and patches themselves in a much more simple methodology than SVN.

[plegrand]

@Tom-Elliott
i wasnt already running git. It’s new for me.
Before i used svn like that :

cd /home/svn/trunk
svn up
cd bin
./installfog.sh 

Now you tell me to use git that i dont know.
my question is just : do i have to use git like that :

cd /home/svn/trunk
git checkout dev-branch
git pull
cd bin
./installfog.sh

Why i have to use git now ?