Installing glpi/config/client
-
- Beiträge: 6
- Registriert: 30 Sep 2024, 20:45
Installing glpi/config/client
I'm having trouble implementing opsi at my work. I downloaded opsi on my VM (virtual machine) and followed the documentation step by step, the "Quick Start" section. After that, I installed the client on the client's (employee's) computer and configured it on the client's machine. However, when I go to implement the product, it doesn't install. I need help with the implementation. If anyone can help me, I'd be grateful.
Screenshots of my screens in opsiconfiged
NOTE: In my opsi-configed, my client doesn't appear as 'ON'.
I can send the opsiconfd logs if necessary.
Screenshots of my screens in opsiconfiged
NOTE: In my opsi-configed, my client doesn't appear as 'ON'.
I can send the opsiconfd logs if necessary.
- j.schneider
- uib-Team
- Beiträge: 1918
- Registriert: 29 Mai 2008, 15:14
Re: Installing glpi/config/client
Hello!
How did you install the opsi-client-agent on the machine?
Please do not use an IP-address as the ID for the client.
Please reinstall the opsi-client-agent on the computer using the opsi-client-agent-installer (you can find it in https://<your-opsi-server>:4447/public/opsi-client-agent/).
On the dialog asking for the Client-ID fill in the FQDN of the computer: <hostname>.<dns-domain>
For example: client1.scalco.local
Use your admin credentials for username and password and click on "install".
How did you install the opsi-client-agent on the machine?
Please do not use an IP-address as the ID for the client.
Please reinstall the opsi-client-agent on the computer using the opsi-client-agent-installer (you can find it in https://<your-opsi-server>:4447/public/opsi-client-agent/).
On the dialog asking for the Client-ID fill in the FQDN of the computer: <hostname>.<dns-domain>
For example: client1.scalco.local
Use your admin credentials for username and password and click on "install".
-
- Beiträge: 6
- Registriert: 30 Sep 2024, 20:45
Re: Installing glpi/config/client
Before this test, I entered the ID during the installation, and followed the step-by-step instructions for entering the FQDN. When I followed these steps, the installation went well, but I still got the error that "ON" did not appear on the client and I was unable to install the product on the machines via the server.
On the client's computer, there was no DNS domain, so I logged into the network and entered a "DNS suffix for this network". Can this be used as a "DNS domain"?
NOTE: I may be sending a screenshot when doing these installation tests with the FQDN
On the client's computer, there was no DNS domain, so I logged into the network and entered a "DNS suffix for this network". Can this be used as a "DNS domain"?
NOTE: I may be sending a screenshot when doing these installation tests with the FQDN
- j.schneider
- uib-Team
- Beiträge: 1918
- Registriert: 29 Mai 2008, 15:14
Re: Installing glpi/config/client
If the computer does not have a DNS suffix, you do not need to change any network settings.
You can simply use any suffix for the client ID.
For example, you can use <hostname>.opsi.internal.
If the installation goes well, but the client still cannot connect to the server, please take a look at the log file c:\opsi.org\log\opsiclientd.log
You can simply use any suffix for the client ID.
For example, you can use <hostname>.opsi.internal.
If the installation goes well, but the client still cannot connect to the server, please take a look at the log file c:\opsi.org\log\opsiclientd.log
-
- Beiträge: 6
- Registriert: 30 Sep 2024, 20:45
Re: Installing glpi/config/client
I tried following the step-by-step instructions you provided, but it didn't work. I downloaded the server again, configured the products on the server, but when I tried to install the client on the client PC, I initially got this error:
However, when I manually enter the address of my server or search for it, the installation succeeds and the installer starts. On the server and client, it looks like this:
I still can't install the products on my client. I've checked the logs, but I don't understand them very well.
However, when I manually enter the address of my server or search for it, the installation succeeds and the installer starts. On the server and client, it looks like this:
I still can't install the products on my client. I've checked the logs, but I don't understand them very well.
- j.schneider
- uib-Team
- Beiträge: 1918
- Registriert: 29 Mai 2008, 15:14
Re: Installing glpi/config/client
Please look for errors in the log file c:\opsi.org\log\opsiclientd.log on the client and post the log here.
-
- Beiträge: 6
- Registriert: 30 Sep 2024, 20:45
Re: Installing glpi/config/client
a part of the log where there are some errors, I'm still trying to install the product, this error seems to be something to do with the connection, could it be something with dhcp?
Code: Alles auswählen
[5] [2024-09-17 17:07:39.482] [ ] Connection to opsi service https://opsiserver.opsi.internal:4447 failed: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0D6AE390>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:282)
[6] [2024-09-17 17:07:39.483] [permanent service connection ] Failed to connect: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0D6AE390>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:225)
[6] [2024-09-17 17:12:39.629] [permanent service connection ] Trying to connect (OpsiService.py:221)
[5] [2024-09-17 17:12:39.631] [ ] Opening connection to opsi service https://opsiserver.opsi.internal:4447 (OpsiService.py:261)
[5] [2024-09-17 17:12:39.641] [ ] Connection to opsi service https://opsiserver.opsi.internal:4447 failed: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0D6AE750>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:282)
[6] [2024-09-17 17:12:39.642] [permanent service connection ] Failed to connect: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0D6AE750>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:225)
[6] [2024-09-17 17:17:40.093] [permanent service connection ] Trying to connect (OpsiService.py:221)
[5] [2024-09-17 17:17:40.095] [ ] Opening connection to opsi service https://opsiserver.opsi.internal:4447 (OpsiService.py:261)
[5] [2024-09-17 17:17:40.108] [ ] Connection to opsi service https://opsiserver.opsi.internal:4447 failed: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0DDB75B0>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:282)
[6] [2024-09-17 17:17:40.108] [permanent service connection ] Failed to connect: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0DDB75B0>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:225)
[6] [2024-09-17 17:22:41.540] [permanent service connection ] Trying to connect (OpsiService.py:221)
[5] [2024-09-17 17:22:41.542] [ ] Opening connection to opsi service https://opsiserver.opsi.internal:4447 (OpsiService.py:261)
[5] [2024-09-17 17:22:41.624] [ ] Connection to opsi service https://opsiserver.opsi.internal:4447 failed: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0D639DD0>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:282)
[6] [2024-09-17 17:22:41.625] [permanent service connection ] Failed to connect: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0D639DD0>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:225)
[6] [2024-09-17 17:27:43.790] [permanent service connection ] Trying to connect (OpsiService.py:221)
[5] [2024-09-17 17:27:43.792] [ ] Opening connection to opsi service https://opsiserver.opsi.internal:4447 (OpsiService.py:261)
[5] [2024-09-17 17:27:43.802] [ ] Connection to opsi service https://opsiserver.opsi.internal:4447 failed: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0DDCE450>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:282)
[6] [2024-09-17 17:27:43.802] [permanent service connection ] Failed to connect: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0DDCE450>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:225)
[6] [2024-09-17 17:32:46.029] [permanent service connection ] Trying to connect (OpsiService.py:221)
[5] [2024-09-17 17:32:46.032] [ ] Opening connection to opsi service https://opsiserver.opsi.internal:4447 (OpsiService.py:261)
[5] [2024-09-17 17:32:46.100] [ ] Connection to opsi service https://opsiserver.opsi.internal:4447 failed: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0DDCFD30>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:282)
[6] [2024-09-17 17:32:46.101] [permanent service connection ] Failed to connect: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0DDCFD30>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:225)
[6] [2024-09-17 17:37:48.259] [permanent service connection ] Trying to connect (OpsiService.py:221)
[5] [2024-09-17 17:37:48.261] [ ] Opening connection to opsi service https://opsiserver.opsi.internal:4447 (OpsiService.py:261)
[5] [2024-09-17 17:37:48.309] [ ] Connection to opsi service https://opsiserver.opsi.internal:4447 failed: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0DDCF0D0>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:282)
[6] [2024-09-17 17:37:48.310] [permanent service connection ] Failed to connect: Opsi service connection error: HTTPSConnectionPool(host='opsiserver.opsi.internal', port=4447): Max retries exceeded with url: /rpc (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x0DDCF0D0>: Failed to resolve 'opsiserver.opsi.internal' ([Errno 11001] getaddrinfo failed)")) (OpsiService.py:225)
[5] [2024-09-17 17:38:08.725] [event generator login_detector ] Logoff: ('TESTE\\TI',) (__init__.py:107)
[6] [2024-09-17 17:38:08.725] [event generator login_detector ] LoginDetector triggered. eventType: 'Logoff', args: ('TESTE\\TI',) (UserLogin.py:79)
[5] [2024-09-17 17:38:09.537] [opsiclientd ] Handling shutdown request (service.py:101)
[5] [2024-09-17 17:38:09.553] [opsiclientd ] Someone triggered a reboot or a shutdown => clearing reboot request (Opsiclientd.py:899)
[5] [2024-09-17 17:38:09.584] [ ] Stopping <OpsiclientdNT6(Opsiclientd, started daemon 3188)> (Opsiclientd.py:712)
- j.schneider
- uib-Team
- Beiträge: 1918
- Registriert: 29 Mai 2008, 15:14
Re: Installing glpi/config/client
The name of the opsi server "opsiserver.opsi.internal" cannot be resolved.
You can add the name to your DNS server or you can use an IP address to connect to the opsi server.
If you want to use an IP address, click on the "server configuration" button in opsi-configed and change the value of "clientconfig.configserver.url" to "https://192.168.1.214:4447".
Then install the opsi-client-agent again.
You can add the name to your DNS server or you can use an IP address to connect to the opsi server.
If you want to use an IP address, click on the "server configuration" button in opsi-configed and change the value of "clientconfig.configserver.url" to "https://192.168.1.214:4447".
Then install the opsi-client-agent again.
-
- Beiträge: 6
- Registriert: 30 Sep 2024, 20:45
Re: Installing glpi/config/client
I performed the configuration as you described, but when I tried to install the client again on the machine, the following error occurred on the client:
The client appears on the server, but the ON part is not set
The client appears on the server, but the ON part is not set
- j.schneider
- uib-Team
- Beiträge: 1918
- Registriert: 29 Mai 2008, 15:14
Re: Installing glpi/config/client
Please deactivate the DHCP-Backend.
Edit the file /etc/opsi/backends/dhcpd.conf on the opsi config server and set
Restart opsiconfd after the change:
Then reinstall opsi-client-agent on the device.
See the documentation for details: https://docs.opsi.org/opsi-docs-en/4.3/ ... r-autoconf
Edit the file /etc/opsi/backends/dhcpd.conf on the opsi config server and set
Code: Alles auswählen
"enabled": False,
Code: Alles auswählen
systemctl restart opsiconfd
See the documentation for details: https://docs.opsi.org/opsi-docs-en/4.3/ ... r-autoconf