Confirmed users
3,990
edits
ReleaseEngineering/OPSI: Difference between revisions
Jump to navigation
Jump to search
→Troubleshooting
| Line 157: | Line 157: | ||
== Troubleshooting == | == Troubleshooting == | ||
=== Check which master === | |||
* Open regedit and browse to HKEY_LOCAL_MACHINE\SOFTWARE\opsi.org\pcptch | |||
* "opsiServiceURL" key should point to XXX for production or "https://10.2.71.216:4447" for staging. | |||
=== Check the hostkey === | |||
* Check that the hostkeys on the master and the slave are the same | |||
** in master: /etc/opsi/pckeys | |||
** in slave: C:\Program Files\opsi.org\preloginloader\cfg\locked.cfg | |||
* the hostkey is generated with a service on boot [[ReferencePlatforms/Win32#OPSI_Hostkey_Generator|Win32#OPSI_Hostkey_Generator]] | |||
** ssh into staging-opsi and check /home/cltbld/opsi-package-sources/hostkey-generator/CLIENT_DATA/hostkey.ins to see what it does | |||
*** TODO where to check the service on the windows machine | |||
=== Check the opsiconfd log === | |||
* select the slave from the OPSI.jar menu | |||
* select the tab that says "Log files" | |||
* select the sub-tab named "opsiconfd" | |||
* go to the bottom to see the latest messages | |||
=== uib.local VS .build.mozilla.org === | |||
bhearsum: it indicates what domain the OPSI server thinks it's in. | |||
it's long standing that it's different between production and | |||
staging, but it shouldn't be an issue | |||
=== Re-installing OPSI === | |||
This is probably not need anymore. Check with bhearsum. | |||
NOTE: This instructions were build up from [[ReferencePlatforms/Win32#Change_OPSI_server_.28staging_slaves_only.29|this]] page. | |||
* change the opsiServiceURL to point to staging (explained above) | |||
* In c:\program files\opsi.org\preloginloader\uninst run deinstall.cmd | |||
** the slave will reboot | |||
* disconnect the mapped drive for production opsi | |||
* install OPSI from staging-opsi | |||
** Start Menu -> Run -> \\10.2.71.216 | |||
** Use 'pcpatch' and the root password when prompted. (Use the geTxxxx password until {{bug|519989}} is solved) | |||
** Right click 'opt_pcbin' and select 'Mount as Network Drive' | |||
** Browse to z:\install\preloginloader | |||
** Double click 'opsi-prep.vbs' (you won't see anything happen) | |||
** Double click 'service-setup.cmd', hit a key when prompted | |||
** When prompted for a username and password use 'root' and the appropriate password (the current one unlike for "pcpatch") | |||
** Press any key (I assume it should have rebooted after this but it didn't - armenzg) | |||
[really? it didn't happen to me - armenzg] OPSI forces reboot on completion of install and then you can manage it through the opsi client. | |||
=== error: HTTP/1.1 401 Unauthorized === | === error: HTTP/1.1 401 Unauthorized === | ||
This error appears before logging in. I believe you can only stop "the installation" and be able to access the machine. | This error appears before logging in. I believe you can only stop "the installation" and be able to access the machine. | ||
| Line 165: | Line 209: | ||
or that the hostkey on the slave doesn't match the one the server. | or that the hostkey on the slave doesn't match the one the server. | ||
I assume we have to check is it is: | |||
* talking to right master | |||
* if the hostkey is the same on the slave and on the master | |||
* | |||
* | |||
=== Wrong hostkey === | |||
Failed to process rpc: opsiHostKey authentication failed for host 'talos-r3-xp-001.build.mozilla.org': wrong key (opsiconfd|623) | |||
* | * check [[ReleaseEngineering/OPSI#|this]] section to fix it. | ||
=== How to update the opt_pcbin drive mapping password - "pcpatch" === | === How to update the opt_pcbin drive mapping password - "pcpatch" === | ||