Topics created by Lenain

@Lenain Just a little FYI.
I don’t know when I’ll have time to test it out fully before putting it into production, but the idea of adding this to the module was not forgotten and I started a branch for it while I was working on some other bug fixes
https://github.com/darksidemilk/FogApi/commit/03c0342cff759ef272a64bbb91cbb1b5999bab9c

@lenain said in AD password issue:

'

Is the “&#039:”. giving a problem? MYSQL is typing it that way as a HTML code. I have no coding knowledge nor do I know MYSQL very well but this may be of some use:
Source:
https://stackoverflow.com/questions/9596652/how-to-escape-apostrophe-in-mysql
Quote:
Possibly off-topic, but maybe you came here looking for a way to sanitise text input from an HTML form, so that when a user inputs the apostrophe character, it doesn’t throw an error when you try to write the text to an SQL-based table in a DB. There are a couple of ways to do this, and you might want to read about SQL injection too. Here’s an example of using prepared statements and bound parameters in PHP:

$input_str = “Here’s a string with some apostrophes (')”;
// sanitise it before writing to the DB (assumes PDO)
$sql = “INSERT INTO table (note) VALUES (:note)”;
try {
$stmt = $dbh->prepare($sql);
$stmt->bindParam(‘:note’, $input_str, PDO::PARAM_STR);
$stmt->execute();
} catch (PDOException $e) {
return $dbh->errorInfo();
}
return “success”;
In the special case where you may want to store your apostrophes using their HTML entity references, PHP has the htmlspecialchars() function which will convert them to “&#039 ;”. As the comments indicate, this should not be used as a substitute for proper sanitisation, as per the example given.

@lenain Ubuntu 14.04 LTS is no longer in support since April 2019.

@Sebastian-Roth Thank you so much! You save my life (almoste 😉 ) It was about ipxe.efi, I have change to realtek.efi in DHCP and now it work fine. Nice work thank you ^_^

@Sebastian-Roth
I have found the error by myself, it was a misconfiguration of the variable no_proxy. I have change it and restart fog, it’s ok now:
export no_proxy=127.0.0.1,IP.OF.SRV.FOG,[…]
Thank you for your help!

Ok @Sebastian-Roth, if it goes wrong again I will tell.
Thanks

@Lenain I think that your only option is develop a new plugin to do this.

@Lenain You are welcome. Does this solve the issue for you?

Moved this to feature requests and marked as unsolved.

Please install the latest rcs of which you’ll find this issue is already fixed.

@Wayne-Workman said in Install FOG 1.3.3 with wget or git:

e

Ok, thank you. I will try 1.3.5 before ending my procedure.

@Tom-Elliott
Thank you, it work fine! Here my po file, it is perfectible but better french than google trad 😉
0_1486735555898_messagesFR3.po

@Tom-Elliott
Hello,
Thanks for your answer, I will wait for 1.3.5 release.

@Joe-Schmitt
It work fine now, thanks.

@Lenain I can’t understand how/why this is a fix. I’m going to update my prod instance fro 1.3.4 and see if I can duplicate it. I’m currently on 1.3.3.

Interesting. Thanks for the tip.

@Tom-Elliott
Work fine, thanks a lot!

@Tom-Elliott
Ok thanks

@Tom-Elliott
Hello,
Fog configuration page:
text alternatif
Fog general settings:
text alternatif
FOG services logs:
text alternatif
servicemaster.log:

[09-14-16 2:23:45 pm] FOGMulticastManager Start [09-14-16 2:23:45 pm] FOGMulticastManager forked child process (18686). [09-14-16 2:23:45 pm] FOGMulticastManager child process (18686) is running. [09-14-16 2:23:47 pm] FOGImageReplicator Start [09-14-16 2:23:47 pm] FOGImageReplicator forked child process (18735). [09-14-16 2:23:47 pm] FOGImageReplicator child process (18735) is running. [09-14-16 2:23:50 pm] FOGImageReplicator Start [09-14-16 2:23:50 pm] FOGImageReplicator forked child process (19050). [09-14-16 2:23:50 pm] FOGImageReplicator child process (19050) is running. [09-14-16 2:23:55 pm] FOGPingHosts Start [09-14-16 2:23:55 pm] FOGPingHosts forked child process (19218). [09-14-16 2:23:55 pm] FOGTaskScheduler Start [09-14-16 2:23:55 pm] FOGTaskScheduler forked child process (19219). [09-14-16 2:23:55 pm] FOGTaskScheduler child process (19219) is running. [09-14-16 2:23:55 pm] FOGPingHosts child process (19218) is running. [09-14-16 2:33:55 pm] FOGTaskScheduler child process (19219) exited with code 255. [09-14-16 2:38:55 pm] FOGTaskScheduler forked child process (21217). [09-14-16 2:38:55 pm] FOGTaskScheduler child process (21217) is running. [09-29-16 12:34:55 pm] Service_Signal_handler (18733) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (18733) killing child (18735). [09-29-16 12:34:55 pm] Service_Signal_handler (18733) exiting. [09-29-16 12:34:55 pm] Service_Signal_handler (18685) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (18685) killing child (18686). [09-29-16 12:34:55 pm] Service_Signal_handler (18685) exiting. [09-29-16 12:34:55 pm] Service_Signal_handler (19199) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (19199) killing child (19218). [09-29-16 12:34:55 pm] Service_Signal_handler (19199) exiting. [09-29-16 12:34:55 pm] Service_Signal_handler (19147) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (19147) killing child (21217). [09-29-16 12:34:55 pm] Service_Signal_handler (19147) exiting. [09-29-16 12:34:55 pm] Service_Signal_handler (18828) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (18828) killing child (19050). [09-29-16 12:34:55 pm] Service_Signal_handler (18828) exiting. [09-29-16 12:35:17 pm] FOGTaskScheduler Start [09-29-16 12:35:17 pm] FOGTaskScheduler forked child process (1718). [09-29-16 12:35:17 pm] FOGTaskScheduler child process (1718) is running. [09-29-16 12:35:17 pm] FOGImageReplicator Start [09-29-16 12:35:17 pm] FOGImageReplicator forked child process (1719). [09-29-16 12:35:17 pm] FOGImageReplicator child process (1719) is running. [09-29-16 12:35:17 pm] FOGMulticastManager Start [09-29-16 12:35:17 pm] FOGMulticastManager forked child process (1720). [09-29-16 12:35:17 pm] FOGMulticastManager child process (1720) is running. [09-29-16 12:35:17 pm] FOGImageReplicator Start [09-29-16 12:35:17 pm] FOGImageReplicator forked child process (1721). [09-29-16 12:35:17 pm] FOGImageReplicator child process (1721) is running. [09-29-16 12:35:18 pm] FOGPingHosts Start [09-29-16 12:35:18 pm] FOGPingHosts forked child process (2195). [09-29-16 12:35:18 pm] FOGPingHosts child process (2195) is running. [09-29-16 12:45:18 pm] FOGTaskScheduler child process (1718) exited with code 255. [09-29-16 12:50:18 pm] FOGTaskScheduler forked child process (5825). [09-29-16 12:50:18 pm] FOGTaskScheduler child process (5825) is running. [09-30-16 12:13:29 pm] Service_Signal_handler (1558) received signal 15. [09-30-16 12:13:29 pm] Service_Signal_handler (1558) killing child (1720). [09-30-16 12:13:29 pm] Service_Signal_handler (1558) exiting. [09-30-16 12:13:31 pm] Service_Signal_handler (1512) received signal 15. [09-30-16 12:13:31 pm] Service_Signal_handler (1512) killing child (1721). [09-30-16 12:13:31 pm] Service_Signal_handler (1512) exiting. [09-30-16 12:13:34 pm] Service_Signal_handler (1535) received signal 15. [09-30-16 12:13:34 pm] Service_Signal_handler (1535) killing child (1719). [09-30-16 12:13:34 pm] Service_Signal_handler (1535) exiting. [09-30-16 12:13:36 pm] Service_Signal_handler (1487) received signal 15. [09-30-16 12:13:36 pm] Service_Signal_handler (1487) killing child (5825). [09-30-16 12:13:36 pm] Service_Signal_handler (1487) exiting. [09-30-16 12:13:38 pm] Service_Signal_handler (1951) received signal 15. [09-30-16 12:13:38 pm] Service_Signal_handler (1951) killing child (2195). [09-30-16 12:13:38 pm] Service_Signal_handler (1951) exiting.

There is a problem, I have no more logs, look at the dates, it seems that since the 1.2 to 1.3 update FOG write nothing.

And I have a issue with all FOG services:
text alternatif

I’ve used fog to change hostnames of computers joined to a domain. It works fine. What’s most likely happening is the credentials you have saved in fog for AD don’t have the authority to disable the old computer objects so new ones can be made.

At any rate - we’re just guessing and won’t be of much help until we can get a c:\fog.log file from an affected host from you.