Closed Bug 596337 Opened 15 years ago Closed 14 years ago

Help with OPSI for Windows 64-bit machine

Categories

(Release Engineering :: General, defect, P4)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: armenzg, Unassigned)

References

Details

(Whiteboard: [opsi][win64])

Attachments

(3 files)

I don't know what else to do. I will read more documentation and dip into the code and hopefully be enlightened. I have followed these instructions: https://wiki.mozilla.org/ReferencePlatforms/Win64#OPSI_Client_.26_AutoIT but I will need someone who actually knows about OPSI to help me with this. There are few things to note as I am not sure that everything got installed properly and I say this because: * in the notes it says that the machine should have forcibly rebooted but it did not * when cshields asked me to uninstall it did not show up on the list of available machines When I look at the logs I see the following: * clientconnect - http://grab.by/6nVX * opsiconfd - http://grab.by/6nW1 When I look at the machines' list I see: * Two machines listed (mw64-ix-slave01.{build.local|build.mozilla.org} - http://grab.by/6nW4 ** This is probably from adding to staging-opsi:~/opsi-packages-sources/staging-slaves the string "mw64-ix-slave01" * mw64-ix-slave01.uib.local shows "preloginloader" installed while the other one shows a bunch of packages installed which I have not done since I can't install anything! it also does not show any logs and has been last heard of on the 7th. I also don't understand what is the process on adding keys to /etc/opsi/pckeys and when to add a slave name on the staging-slaves file. This output is from /c/tmp/opsiclientd.log [3] [Sep 14 11:31:49] [opsiclientd] Refusing to set empty value for config value 'block_notifier_command' of section 'opsiclientd_notifier' (opsiclientd.pyo|2161) [0] [Sep 14 11:31:49] [opsiclientd] Opsiclientd version: 0.5.7.4 (opsiclientd.pyo|2549) [0] [Sep 14 11:31:49] [opsiclientd] Commandline: C:\Program Files (x86)\opsi.org\preloginloader\opsiclientd.exe (opsiclientd.pyo|2550) [0] [Sep 14 11:31:49] [opsiclientd] Working directory: C:\Windows\system32 (opsiclientd.pyo|2551) [2] [Sep 14 11:32:16] [opsiclientd] Failed to get rebootRequested from registry: [Error 2] The system cannot find the file specified (opsiclientd.pyo|3188)
Attached image double entries
Attached image opsiconfd
The first thing that I noticed is that the shared mount (Z:) is pointing to the production server, but you're trying to verify things (AFAICT) on the staging server. AIUI, you should be connecting to staging-opsi running with clean configs which *should* be equivalent to the production setup.
Coop is right, the mount should be off of the OPSI server you intend to connect to (it is not absolutely necessary, but right now it is the best way to be sure that the version of packages you are trying to install is what the OPSI server is setup for). Speaking of versions - if you are still having problems let me know what version everything is set at again (from the correct server), the OPSI server version and the preloginloader versions are both key here. If you are trying to set this up against staging-opsi and it is a little out of date, that may be the problem here. I have tested Windows Server 2008 R2 64bit against OPSI server 3.4.0.2 and preloginloader 3.4 v27mozilla2
The version for staging-opsi is 3.4.0.0 and I don't see preloginloader installed on the win64-ix-ref.build.mozilla.org machine. Nevertheless when I click on the package I get 3.4 v27mozilla2.
Setting a priority to get it out of the triage pool.
Priority: -- → P4
I tried a few things without success: - preloginloader 3.4-27mozilla2 and 3.4-30 -- These versions successfully talked to the config server but failed to mount the SMB share. Errors were like this: [5] [Oct 20 09:43:11] [action_processor_starter.exe] (2250, 'WNetCancelConnection2', 'The network connection could not be found.') (Windows.pyo|237) [4] [Oct 20 09:43:11] [action_processor_starter.exe] Mounting '\\production-opsi\opt_pcbin' to 'P:' (Windows.pyo|239) [2] [Oct 20 09:43:12] [action_processor_starter.exe] Cannot mount: (1312, 'WNetAddConnection2', 'A specified logon session does not exist. It may already have been terminated.') (Windows.pyo|253) [1] [Oct 20 09:43:12] [action_processor_starter.exe] Traceback: (Logger.pyo|647) [1] [Oct 20 09:43:12] [action_processor_starter.exe] line 71 in '<module>' in file 'action_processor_starter.py' (Logger.pyo|647) [1] [Oct 20 09:43:12] [action_processor_starter.exe] line 254 in 'mount' in file 'OPSI\System\Windows.pyo' (Logger.pyo|647) [1] [Oct 20 09:43:12] [action_processor_starter.exe] ==>>> Cannot mount: (1312, 'WNetAddConnection2', 'A specified logon session does not exist. It may already have been terminated.') (action_processor_starter.py|83) [6] [Oct 20 09:43:12] [action_processor_starter.exe] Executing jsonrpc method 'setStatusMessage' (JSONRPC.pyo|225) [6] [Oct 20 09:43:12] [action_processor_starter.exe] Options: {'params': "Failed to process action requests: Cannot mount: (1312, 'WNetAddConnection2', 'A specified logon session does not exist. It may already have been terminated.')"} (JSONRPC.pyo|229) [7] [Oct 20 09:43:12] [action_processor_starter.exe] Appending param: Failed to process action requests: Cannot mount: (1312, 'WNetAddConnection2', 'A specified logon session does not exist. It may already have been terminated.'), type: <type 'str'> (JSONRPC.pyo|238) [7] [Oct 20 09:43:12] [action_processor_starter.exe] jsonrpc string: {"params":["Failed to process action requests: Cannot mount: (1312, 'WNetAddConnection2', 'A specified logon session does not exist. It may already have been terminated.')"],"id":1,"method":"setStatusMessage"} (JSONRPC.pyo|248) [7] [Oct 20 09:43:12] [action_processor_starter.exe] requesting: 'https://localhost:4441/opsiclientd', query '{"params":["Failed to process action requests: Cannot mount: (1312, 'WNetAddConnection2', 'A specified logon session does not exist. It may already have been terminated.')"],"id":1,"method":"setStatusMessage"}' (JSONRPC.pyo|250) [6] [Oct 20 09:43:12] [action_processor_starter.exe] Using method POST (JSONRPC.pyo|283) I also tried preloginloader 3.4-69, which failed to event connect the config server -- claimed that it timed out.
We have decided to create the pool without OPSI. We will have to add a package management solution on Q2. We might do puppet for Windows. We'll see.
Blocks: support-win64
No longer blocks: 565402
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: