Posts made by Claude Girard

@Tom-Elliott
Yes solved
Thank you

@Tom-Elliott said:

Fairly sure this is still fixed, and with the added benefit of properly getting the snapins from all nodes within.

Sorry but Rev 6885, again blank page in create snapin and edit snapin.

Apache error log (same error in crating or in editing snapin):

[Mon Mar 21 08:33:21.445380 2016] [:error] [pid 2066] [client 172.20.40.1:39732] PHP Fatal error: Call to a member function chdir() on null in /var/www/html/fog/lib/fog/fogbase.class.php on line 74, referer: http://crim-fog.pu-pm.univ-fcomte.fr/fog/management/index.php?node=snapin&sub=list

@Tom-Elliott Yes. It exist.
On this screen capture is what I can see.
And when I create or update the snapin, if I download the file on my computer, and choose it for re-upload, on my server group owner for this file become “fog”, before it was “www-data”

Yes it’s ok for me too.

But I don’t know if you wanted that, now when I create or modify a snapin, I have no more choice box, for choosing what file present on server I want to use.
I can only upload.
so I can’t create a snapin from another one without downloading file, then reuploading it

Hi

When I want to add or modify a snapin, I see a blank page.
In apache error log I have these lines:

[Fri Mar 18 09:54:19.887823 2016] [:error] [pid 2559] [client 172.20.40.1:55816] PHP Fatal error: Call to a member function chdir() on null in /var/www/html/fog/lib/fog/fogbase.class.php on line 73, referer: http://crim-fog.pu-pm.univ-fcomte.fr/fog/management/index.php?node=snapin&sub=list

[Fri Mar 18 09:54:22.237175 2016] [:error] [pid 2604] [client 172.20.40.1:55818] PHP Strict Standards: Accessing static property FOGPageManager::$FOGSubMenu as non static in /var/www/html/fog/lib/fog/fogpagemanager.class.php on line 35, referer: http://crim-fog.pu-pm.univ-fcomte.fr/fog/management/index.php?node=snapin

Hi,

For some images, I see this error when deploying:
No drive number passed restoreAllEBRs

Tom, in src/buildroot/package/fog/scripts/usr/share/fog/lib/partition-funcs.sh you forgot to rename a variable used in a test in RestoreAllEBRs function:
line 265 variable is named disk_number
line 270 test is made on drivenum

@Jbob said:

@ch3i @Matthieu-Jacquart
I have a potential patch made. If either you are willing to try it, send me a chat message and I’ll send you the nightly installer.

Same bug win 8.1:
Client 0.9.10

01/02/2016 10:48 RegistryHandler ERROR: Could not set SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerNameComputerName
01/02/2016 10:48 RegistryHandler ERROR: Impossible de créer une sous-clé stable sous une clé parente volatile.

Maybe missing antislash between ActiveComputerName and ComputerName ?
Does the patch solve the issue ?

@Tom-Elliott
Yes but that wasn’t the problem.
In funcs.sh script, I saw:
case $osid in
[1-2])
.
.
.
[5-7]|9)
.
.

And missing *) in the case test, so only 1,2,5,6,7,9 partition types were correctly tested.
And my image was 50 type (linux)

But these lines in funcs.sh have been totally rewrited, now the last case test is present

Thx

I don’t know from which rev, but this issue is solved

Hi Tom

I think line 55 in service_lib.php should be:
sleep((int)$service_sleep_time);

Hi,

Rev 5968 but this issue seems to be present since Rev 5909 commit 2872cf5e99f0cba6f3cdcbe18d8dd1ab40347b4c

When deploying an image, fog doesn’t find mbr file.
In deploy debug mode, mbrfile is empty.
I saw this issue with os type = linux. If I change this in os type= windows 8.1, mbr file is found.

In funcs.sh, test on os type is made only for 1, 2 , 5 , 6 ,7 and 9 os type.

Semms to be solved in rev 5664
Thanks

Hi,

Rev 5624, when I want to run a snapin task, I see this error:
Fatal error: Call to a member function get() on null in /var/www/html/fog/lib/fog/host.class.php on line 550
Reversing this line to previous version resolve the issue.

Maybe because it isn’t an imaging task ?

@Tom-Elliott said:

@Scott-B where are the \r\n lines doing? Or was this file edited/opened by Windows?

Hi Tom

I think this is because of escaped characters again.
May I open a specific thread for these problems ?

I have these \r\n for example in image description when I write this text on several lines, with return between each one.

I saw escaped problems in:
snapins fields
PXE menu
host or image description

Maybe could be the same in other fields

And what is problematic:
french accents é, à , ê, etc …
antislashes
&
Line feed and/or carriage return
Maybe more …

Sometimes I can see that in database, but not in FOG interface (for example \r\n isn’t visible in fog interface but is in database)
Sometimes I can see in both (for example for french accents)

Can you verify in fog database, GLobal settings table, settingkey FOG_PXE_ADVANCED, and see if these lines are the same in database ?

Maybe same problem than:
https://forums.fogproject.org/topic/5752/new-client-some-snapins-doesn-t-work-ok-with-legacy-client/15

where && become &\amp;

I remember that advanced menu didn’t work and host booted on hard drive

@Tom-Elliott said:

I’ve removed the dirname function from the stuff, if you can update and let me know if things are good?

Yes it’s ok now

Thank you

Rev 5307
I wanted to test new client version (0.9.6), and snapins did’nt work.
In log file I could see:
Failed to find snapin file

With a colleague help, we found the problem: snapin file was searched with path /opt/fog
And snapins are in /opt/fog/snapins

In Global configuration, I have /opt/fog/snapins/ for FOG_SNAPDIR (with the trailing slash)

But in Storage configuration, for each node I have /opt/fog/snapins (without trailing slash)

And in lib/client/SnapinClient.class.php line 36 you use dirname
Dirname without trailing slash extract only the first part (/opt/fog/)

And in commons/schema.php, line 1642, value is forced to /opt/fog/snapins (without trailing slash)
In Storage configuration, if I add trailing slash, it dissapear after validation.

@Jbob said:

@Claude-Girard v0.9.6 is released, and this includes the snapin fix for the problem you originally posted on. (https://news.fogproject.org/client-v0-9-6/ )

Thank you.
I just tested and for me it’s ok.
You can mark this thread solved, but I will open a new one for the others problems, discussed with Tom, they are’nt solved.
And I found a snapin bug again, but not due to client.

Thanks again

@Tom-Elliott said:

I wasn’t confused about the language, I was confused what Advanced menu had to do with snapins, but ultimately it didn’t matter really. I understood what you were getting at and I was able to make the corrects to ensure things operated properly. Hopefully it’s much better for all things.

Yes but better english = better explanations !!!
Did you push these corrects on github ?
I just upgraded rev 5283 and i don’t notice any change.

@Tom-Elliott said:

@Claude-Girard I found and believe I have fixed the issue (for all items fingers crossed).

I just pushed it to the wild too.

Thank you and sorry for confusing you, maybe my english is too bad