Yes, it works.
Thanks a lot.
Adrien17
Posts made by adrien17
-
FOG service is too long to stop
Hello,
on my clients Linux - Ubuntu 20 and CentOS 7 - when I stop FOGService, it takes exactly 1m30 to stop.
The version on the server is FOG 1.5.8 and the version on the clients is 0.11.19
I have not found any parameter which could explain that long time.
Thanks for your help,
Adrien17 -
RE: I can't install the Fog client on CenOS 8
@Sebastian-Roth said in I can't install the Fog client on CenOS 8:
https://www.mono-project.com/download/stable/#download-lin-centos
Thanks a lot. With this method it works.
-
RE: I can't install the Fog client on CenOS 8
Hum again. The packages that are to be installed are those of CentOS 7, and I should uninstall some packages on my CentOS 8, such as giflib and emacs, in order to install the mono packages…
The repo download.mono-project.com_repo_centos_ does not provide packages for CentOS 8 -
RE: I can't install the Fog client on CenOS 8
Hum. I’m quite sorry, I just see the solution on the Fog wiki; it works
(so you can add CentOS 8 in the list of Linux distros). -
I can't install the Fog client on CenOS 8
To install the Fog client, I used ‘mono SmartInstaller.exe’. But for CentOS 8, the rpm’s mono are now on the repo https://extras.getpagespeed.com/redhat/8/$basearch/
and I must pay to get them -which is not possible in my university.
I have tried to use the command mono that comes from the package of CentOS 7, but it does not work : the messages areUnhandled Exception: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542 at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x0002b] in <1fd744d936be4a229b315d57c3b96c68>:0 at System.TermInfoReader..ctor (System.String term, System.String filename) [0x00065] in <1fd744d936be4a229b315d57c3b96c68>:0 at System.TermInfoDriver..ctor (System.String term) [0x00058] in <1fd744d936be4a229b315d57c3b96c68>:0 at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <1fd744d936be4a229b315d57c3b96c68>:0 at System.ConsoleDriver..cctor () [0x00062] in <1fd744d936be4a229b315d57c3b96c68>:0 --- End of inner exception stack trace ---
Is there another solution than using mono packages ?
-
RE: CentOS 7 client fails to connect
Okay, now the client gets the information from the server without error and can execute a task launched from the server.
Thanks a lot. -
RE: CentOS 7 client fails to connect
No, there is not the 302 redirect in the log. It’s as if the server receives no demand from the client.
I don’t find the IP address of the client in the other files in /var/log/httpd. -
RE: CentOS 7 client fails to connect
The result is the same:
on the client the message error is again
“Communication ERROR: SSL connection error: System.Security.Cryptography.X509Certificates.X509ChainStatus[]”
and on the server nothing is logged. -
RE: CentOS 7 client fails to connect
@Sebastian-Roth said in CentOS 7 client fails to connect:
wget --no-check-certificate https://fogus/fog/management/other/ssl/srvpublic.crt
The log on the server is:
148.60.3.96 - - [27/Jan/2020:17:02:17 +0100] "GET /fog/management/other/ssl/srvpublic.crt HTTP/1.1" 200 1749 "-" "Wget/1.14 (linux-gnu)"
-
RE: CentOS 7 client fails to connect
We do not use a custom certificate.
I have installed this new version on the client. The error message in fog.log is now :--------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 1/27/2020 2:29:04 PM Client-Info Version: 0.11.18 1/27/2020 2:29:04 PM Client-Info OS: Linux 1/27/2020 2:29:04 PM Middleware::Authentication Waiting for authentication timeout\ to pass 1/27/2020 2:29:04 PM Middleware::Communication Download: https://fogus/fog/management/other/ssl/srvpublic.crt 1/27/2020 2:29:05 PM Middleware::Communication ERROR: SSL connection error: System\.Security.Cryptography.X509Certificates.X509ChainStatus[] 1/27/2020 2:29:05 PM Middleware::Communication ERROR: Could not download file 1/27/2020 2:29:05 PM Middleware::Communication ERROR: Error: TrustFailure (Authentication failed, see inner exception.)
On the server, I have had a log (in /var/log/httpd/access_log) when I installed the client :
148.60.3.96 - - [27/Jan/2020:14:16:38 +0100] "GET /fog/management/other/ca.cert.der HTTP/1.1" 200 1287 "-" "-" 148.60.3.96 - - [27/Jan/2020:14:16:39 +0100] "GET /fog/management/other/ssl/srvpublic.crt HTTP/1.1" 302 237 "-" "-" 148.60.3.96 - - [27/Jan/2020:14:18:39 +0100] "GET /fog/management/other/ssl/srvpublic.crt HTTP/1.1" 302 237 "-" "-"
But, after, when I restart the Fog service on the client, nothing is logged on the server.
-
CentOS 7 client fails to connect
My server Fog (CentOS is in Https. On the client (CentOS 7) when I start the Fog service, I get in its log:
--------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 1/27/2020 11:16 AM Client-Info Version: 0.11.17 1/27/2020 11:16 AM Client-Info OS: Linux 1/27/2020 11:16 AM Middleware::Authentication Waiting for authentication timeout to pass 1/27/2020 11:18 AM Middleware::Communication Download: https://fogus/fog/management/other/ssl/srvpublic.crt 1/27/2020 11:18 AM Middleware::Communication ERROR: Could not download file 1/27/2020 11:18 AM Middleware::Communication ERROR: Error: TrustFailure (Authentication failed, see inner exception.)
In the log of the server /var/log/httpd/access_log, nothing is reported for that client.
So the client receives no information about the tasks on the server.
Another thing is the status of the Fog service on the client: this status claims that the file /opt/fog-service/service.lock does not exist. But it exists and contains the Pid of the process.
systemctl status FOGService -l ● FOGService.service - FOGService Loaded: loaded (/usr/lib/systemd/system/FOGService.service; disabled; vendor preset: disabled) Active: active (exited) since Mon 2020-01-27 11:16:16 CET; 3min 48s ago Process: 2933 ExecStart=/opt/fog-service/control.sh start (code=exited, status=0/SUCCESS) Main PID: 2933 (code=exited, status=0/SUCCESS) Tasks: 11 CGroup: /system.slice/FOGService.service └─2936 /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe /opt/fog-service/FOGService.exe -d:/opt/fog-service/ -l:/opt/fog-service/service.lock Jan 27 11:16:16 admin14 systemd[1]: Starting FOGService... Jan 27 11:16:16 admin14 control.sh[2933]: cat: /opt/fog-service/service.lock: No such file or directory Jan 27 11:16:16 admin14 control.sh[2933]: starting fog-service Jan 27 11:16:16 admin14 control.sh[2933]: fog-service started
Thanks for your help.
-
RE: Auto log off doesn't work
Hello,
I have installed xprintidle by rpm. Now there is no more error in the user log; however, the auto-logout does not happen.
In the user config, I activate the screensaver, but not the suspend. -
RE: Auto log off doesn't work
Hello,
I have installed libXScrnSaver-devel (by dnf) and xprintidle (by pip).
The file xprintidle.py is in /usr/lib64/python-2.7/site-packages.
But on the user log I have:
—AutoLogOut—
User ERROR: Unable to get user inactivity time
User ERROR: ApplicationName=‘xprintidle’, CommandLine=‘’, CurrentDirectory=‘’, Native error= Cannot find the specified fileI tried to install xprintidle under python3.5 by “pip3 install xprintidle” but this fails.
Thanks for all -
RE: Auto log off doesn't work
Hello,
on Fedora 25 - 26 and on CentOS-7, it doesn’t work.
The file fog.log does do contain the logout feature.
This file is:
[0_1519229981151_fog.log](Uploading 100%)
Thanks.