hi Darren regarding the sysevent stuff, because it depends on a more complex fix that likely won't be available for awhile (allowing nonprivileged users access to event channels), I'm going to switch the event messaging to use standard System V message queues. I'm doing final testing and hope to push today, but once done the sysevent permissions problems should disappear. One change that's visible to you: I thought it might make things easier to follow the picea approach of having a "wait for next event" function, so instead of registering a callback, you can just call
nwam_error_t nwam_event_wait(nwam_event_t *); ...and then call nwam_event_free(nwam_event_t) when you're done with the event. Saves having to deal with cancelling threads etc. So no callback is passed into nwam_events_init(). I updated the library README, so it'll describe all this when I push the changes later, and nwamadm.c will show example usage of the event APIs via the "interact" subcommand. Sorry for the hassle, Alan Darren Kenny wrote: > Hi Anurag, > > On reboot this morning, I found that I was getting some errors when running > the > netcfg service along the lines of: > > "cannot interpret user property" > > This seemed to be down to missing netadm and netcfg users in my /etc/passwd. > > So I added those from an older build, then I got a similar error on groups, > and > so I added them. > > What was different between this and older BFUs was that this was based on a > LU-ed snv_109 from snv_107, which never had these users. I did run acr, which > didn't report any errors to me - I would have expected this to merge the > passwd, > shadow and group files but it didn't.... > > This is making me wonder if there is some other auths or similar missing, > which > weren't merged with BFU, that is causing the sysevent errors... (more below). > > Anurag S. Maskey wrote: > >>> BUT, I am seeing messages like: >>> >>> dlmgmtd[100020]: [ID 498274 daemon.warning] dlmgmt_post_sysevent(3) failed: >>> Permission denied >>> >>> >> I see this dlmgmtd warning in my debug logs. This is generated during >> boot time. I think Alan's recent "fix libsysevent to use auths so that >> setuid(0) hacks can be removed from nwamd" introduced this, but I'm not >> familiar with the sysevents area. >> > > I disabled netcfg, nwam and network/location, cleaned up the nwam > configuration, > and set upgraded to false and then re-enabled these services. This seems to > be a > cleaner configuration than what I already had (which should have also been an > upgraded configuration though... but seemed to be missing some NoNet and > Automatic locations, etc., but they are there now) > > After this, I saw some more messages in the debug log that seemed to suggest > that it was working more as expected, but then I saw the same errors that > Anurag > noticed w.r.t. nwamd restarting, in this light I picked up several core files, > they are all slightly different (attached is a series of pstacks) one common > point appears to be with umem: > > feef5e05 _lwp_kill (2, 6, febfee3c, fee9a5de) + 15 > fee9a5ea raise (6, fef90698, fee64110, fecd77b8) + 22 > fecd77da umem_do_abort (fedb0200) + 2e > fecd79c3 umem_err_recoverable (fece6670, fecfdc68, 80a7908, fece6698) + 4f > fecd9a44 process_free (80a7908, 1, 0, 80b0a94) + e4 > fecd9a7a free (80a7908, 2, febfef0c, fe8b48a8) + 1a > fe8b48ba nv_free_sys (fe8c92c0, 80a7908, 30, fe8b4fae) + 1e > fe8b4a69 nv_mem_free (8089908, 80a7908, 30, 80a7910) + 1d > fe8b4c8a nvp_buf_free (80898e8, 80a7910, febfef6c, fe8b503e) + 22 > fe8b5077 nvlist_free (80898e8, 8074a08, febfef9c, fe9e2b70) + 47 > fe9e2b87 nwam_free_object_list (80898e8, 80b0a94, febfefbc, fe9dd316) + 23 > fe9dd337 nwam_loc_free (80ab188, 80b0b48, febfefcc, 805a3c8) + 2b > 0805a44b nwamd_event_handler (0, fef85000, febfefec, feef088e) + 8f > feef08c6 _thrp_setup (fedb0200) + 7e > feef0b50 _lwp_start (fedb0200, 0, 0, feef088e, 0, 0) > > and there are others without reference to umem. > > I also noticed the message in my logs of: > > nwamd[102635]: [ID 481907 daemon.info] 4: sysevent_bind_handle: Permission > denied > > so it looks like the sysevent stuff isn't working correctly here. > > I also have messages about importing my known wlans, like: > > dub04wlan: could not add to known WLAN: unknown error > > repeating for each known wlan entry from the 0.5 config file: > > dub04wlan 0:13:c3:58:84:f0 > sunwifi 0:18:b0:81:eb:c0 > INSECURE 0:13:19:15:2f:80 > E2-194 0:1a:70:62:8a:e0 > attwifi 0:19:a9:79:ff:40 > Parc 55 0:f:cc:24:ce:40 > dub04wlan 0:13:c3:58:80:40 > dub04wlan 0:13:c3:45:70:80 > dub04wlan 0:13:c3:58:83:f0 > dub04wlan 0:13:c3:45:6c:c0 > dub04wlan 0:13:c3:58:98:d0 > dub04wlan 0:13:c3:58:99:60 > dub04wlan 0:13:c3:58:98:50 > DarrenLucanWLAN 0:15:e9:27:4:1e > > In the end, I'm still not getting any running network - I have to set up > things > manually still. > > Attached is the nwamd debug log for todays session... > > Thanks, > > Darren. >
