[wpkg-users] Problems with WPKG after settings update

[Jens Geile]

Hi, 

> You should look in log.your_machinename, not log.nmbd and log.smbd 
> (unless you have some weird Samba configuration and everything gets 
> logged into log.smbd? That makes the log file very big and unreadable).
There was basically only the test client that was accessing the samba server. So the logfile is pretty much the same as it would've been if samba was configured to create separate logfiles for every machine.

> Is the time on the server and on the workstation in sync?
Yes.

> Because the log file ends earlier than the error from the Event Log (14:48:55).
The following lines from log.smbd are already past the time of the eventlog entry:

[...]
[2008/12/18 14:48:49, 3] printing/pcap.c:pcap_cache_reload(223)
  reload status: ok
[2008/12/18 14:49:38, 3] smbd/sec_ctx.c:set_sec_ctx(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/12/18 14:49:42, 3] smbd/sec_ctx.c:set_sec_ctx(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/12/18 14:49:49, 3] smbd/sec_ctx.c:set_sec_ctx(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[...]

> I don't see anything unusual in the logfile. The workstation was reading some files from the wpkg share etc. Are you sure it is the log from the "failed attempt"?
The second (shorter) paragraph is from a failed attempt, yes. The first one is from a working attempt.

> Workstation did not read (or tried to read) the settings.xml file though.
Settings.xml is only read during installation of wpkg or when the client config is updated. This error isn't really related to wpkg updating its own config as I first thought. It appears to be a more fundamental error as there aren't any traces of wpkg in the samba logs when wpkg failed.
Maybe I can do some more testing tomorrow but I cannot promise anything yet.

-
jens