Config Server with Local Depot

[mansukhpatel]

Hi,

I have a setup a config server with a local depot registered following the two helpful manuals.

I deployed the agent to a machine from the local depot which installed successfully. I am able to reboot etc but when it comes to deploying a packages or running a software/hardware audit the client machine is unable to contact the config server. For some reason its pointing to the wrong config server i.e. instead of https://172.16.100.32:4447/rpc its trying to connect to https://192.168.100.190:4447/rpc

Please advise

[d.oertel]

Hi,

this could happen if the opsi-client-agent was installed at the depot server before the server was regitered as depot.
So the Url to the opsi-client configuration file (/opt/pcbin/install/opsi-client-agent/files/opsi/cfg/config.ini) points to the depot- and not to the config server.

Two possibilities:
1. Edit this file - and redeploy the opsi-client-agent
2. Just reinstall the opsi-client-agent packages - and redeploy the opsi-client-agent

regards

d.oertel

[mansukhpatel]

Hi,

this could happen if the opsi-client-agent was installed at the depot server before the server was regitered as depot.
So the Url to the opsi-client configuration file (/opt/pcbin/install/opsi-client-agent/files/opsi/cfg/config.ini) points to the depot- and not to the config server.

Two possibilities:
1. Edit this file - and redeploy the opsi-client-agent
2. Just reinstall the opsi-client-agent packages - and redeploy the opsi-client-agent

regards

d.oertel

Thanks for the reponse. Now its attempting to contact the server but failing with "Failed to connect to config server 'https://172.16.100.32:4447/rpc': Opsi authentication error: Forbidden: Backend authentication error"

Before I look into this further, I need to ensure that this will work for us for what I am trying to achieve. Below is how I got it setup

We have a number of sites not part of the same domain i.e Site A: abc.local and Site B: xyz.local. I have setup a config server which sits in the cloud and its configured as server1.opsi.local and the depot server is configured as server2.opsi.local.

What I need to be able to do is to be able to audit the various sites and centrally have control to deploy software packages so that all the sites have the standard applications on the same version.

From the error I received above it seems like having the opsi server on a different domain may cause all sorts of authentication issues, correct me if I am wrong...

If the way how I have configured is incorrect, then how would I go about setting it up for our multi domain environment i.e if its possible

[d.oertel]

Hi,

did you register the depot server at the config-server using
opsi-setup --register-depot
?

Set the pcpatch password again:
opsi-admin -d task setPcpatchPassword

The password should be set also at depots.
If it does not work - execute the command above at the depots.

regards

d.oertel

[mansukhpatel]

Hi,

did you register the depot server at the config-server using
opsi-setup --register-depot
?

Set the pcpatch password again:
opsi-admin -d task setPcpatchPassword

The password should be set also at depots.
If it does not work - execute the command above at the depots.

regards

d.oertel

Hi the depot server was registered on the local server following your manual "http://download.uib.de/opsi_stable/doc/ ... ble-en.pdf" chapter 10.2

I tried registering the depot server from the config server but its stuck as shown below:
[5] [Dec 09 17:34:43] Testing connection to config server as user 'opsimaster.opsi.local' (opsi-setup|2286)
[5] [Dec 09 17:34:43] Successfully connected to config server as user 'opsimaster.opsi.local' (opsi-setup|2291)
[5] [Dec 09 17:34:43] Updating backend config '/etc/opsi/backends/jsonrpc.conf' (opsi-setup|2293)
[5] [Dec 09 17:34:43] Backend config '/etc/opsi/backends/jsonrpc.conf' updated (opsi-setup|2305)
[5] [Dec 09 17:34:43] Updating dispatch config '/etc/opsi/backendManager/dispatch.conf' (opsi-setup|2307)
[5] [Dec 09 17:34:43] Dispatch config '/etc/opsi/backendManager/dispatch.conf' updated (opsi-setup|2320)
[5] [Dec 09 17:34:43] Setting rights (opsi-setup|392)

[d.oertel]

Hi,

this looks ok.

Did you set the pcpatch password:
opsi-admin -d task setPcpatchPassword
?

regards

d.oertel

[Earwain]

Hi,

I had the same problem.
opsi-setup --register-depot seems to hang at the last line, and afterwards, the OPSI web interface became unavailable.
The issue survived a cold start.

Further investigation showed that the register-depot action had changed the backend setup (/etc/opsi/backendManager/dispatch.conf)
The file was completely altered and now had only lines refering to JSON using a mysql backend).

I changed the file back to what it should contain, and not only did opsiconfd resumed working, but the depot is now registered and available as well!

HTH,
Krgds
Koen, Neddine.

[d.oertel]

Hi

Further investigation showed that the register-depot action had changed the backend setup (/etc/opsi/backendManager/dispatch.conf)
The file was completely altered and now had only lines refering to JSON using a mysql backend).

That is correct. A depot server has no own data backend. So any webservice call to this server should be redirected to the config server via the JSON Backend.

Could you please post that dispatch.conf

regards

d.oertel

[mansukhpatel]

Hi,

I had the same problem.
opsi-setup --register-depot seems to hang at the last line, and afterwards, the OPSI web interface became unavailable.
The issue survived a cold start.

Further investigation showed that the register-depot action had changed the backend setup (/etc/opsi/backendManager/dispatch.conf)
The file was completely altered and now had only lines refering to JSON using a mysql backend).

I changed the file back to what it should contain, and not only did opsiconfd resumed working, but the depot is now registered and available as well!

HTH,
Krgds
Koen, Neddine.

Hi Sorry for the late response

I changed the dispatch.conf back to its original state and reboot the both the depot and config server but the OPSI web interface is not available on both servers. Again it hangs at line [5] [Dec 09 17:34:43] Setting rights (opsi-setup|392).

I have reset the pcpatch password "opsi-admin -d task setPcpatchPassword" but this hasnt help

[Earwain]

Hi Patel,

Sorry for the late reply from my side.
With regards to the previous post, I have to take back my suggestion. The backend conf file is indeed changed to JSONRPC and that's how it should work.

No idea why it didn't with me the first time I tried. I checked now, and the backed conf file is using JSONRPC and all is working well.
Also, register-depot no longer hangs the server when setting rights.

In the mean time, both depot & config servers are using more recent OPSI packages, maybe this was a bug that's fixed in the mean time?

Sorry if I confused you, I was just trying to help, even though an OPSI beginner myself.

Krgds
Koen