pycap starts to run but then exits causes weewx to fail again.
interceptor: ServerThread: start sniff server
engine: Loading service w
interceptor: MainThread: shutting down server thread
interceptor: MainThread: stop sniff server
interceptor: MainThread: unable to shut down server thread
engine: Caught unrecoverable exception in engine:
**** Empty module name
**** Traceback (most recent call last):
**** File "/usr/share/weewx/weewx/engine.py", line 888, in main
**** engine = engine_class(config_dict)
**** File "/usr/share/weewx/weewx/engine.py", line 78, in __init__
**** self.loadServices(config_dict)
**** File "/usr/share/weewx/weewx/engine.py", line 142, in
loadServices
**** self.service_obj.append(weeutil.weeutil._get_object(svc)(self,
config_dict))
**** File "/usr/share/weewx/weeutil/weeutil.py", line 1107, in
_get_object
**** mod = __import__(module)
**** ValueError: Empty module name
**** Exiting.
libpcap fails completely
engine: Import of driver failed: in method 'pcapObject_open_live', argument
2 of type 'char *' (<type 'exceptions.Type
Error'>)
All of this points to the weewx engine but non of it makes any sense
because I can run interceptor standalone.
I really can't understand how any of this broke in a years time... I have
done plenty of apt upgrades and nothing like this has ever happened and I
have worked on my skin more then once and again no issues.
Guess running weewx is in the past now.... I have tried everything and it
refuses to run.
On Saturday, January 11, 2020 at 6:26:06 PM UTC-8, mwall wrote:
>
>
>
> On Saturday, January 11, 2020 at 4:51:30 PM UTC-5, Scott Grayban wrote:
>>
>> I tried pycap and that did run for a few seconds.
>>
>> Jan 11 00:39:13 weewx-pi weewx[3942]: engine: Loading station type
>> Interceptor (user.interceptor)
>> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: driver
>> version is 0.49
>> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: device
>> type: observer
>> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: sensor
>> map: None
>> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: mode is
>> sniff
>> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: sniff
>> iface=wlan0 promiscuous=0
>> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: sniff
>> filter 'src 10.3.141.62 and dst port 80'
>> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: MainThread: pypcap
>> (1.2.2)
>> Jan 11 00:39:13 weewx-pi weewx[3942]: interceptor: ServerThread: start
>> sniff server
>>
>
> this is actually running just fine - when you ran it this time, there was
> no exception at pcapObject_open_live
>
> so one time when you started weewxd, you got a type error for argument 2
> of pcapObject_open_live. we do not know what caused that.
>
> another time when you started weewxd, you got a failure because of a bogus
> service configuration in your weewx configuration file.
>
> and one time when you ran interceptor directly, it worked.
>
> you did an apt update, which might have updated your pcap library
>
> you updated the interceptor driver
>
> the pcap initialization code in the interceptor driver has not changed
> since january 2019.
>
> so without more information, i'd guess that the failures are due to
> changes that you are making in your weewx configuration file.
>
> if it is true that running interceptor directly works, but running weewxd
> fails, with absolutely no other changes, then run those two different ways
> to figure out what is different.
>
> m
>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/12bab845-adf7-4fb5-b116-f284dea63dd6%40googlegroups.com.
