[weewx-development] Re: weewx-multi issues

2017-09-06 Thread gjr80
Hi Peter,

Yes I did look at those and both were unremarkable and then promptly forgot 
to mention them. FWIW following is their output:

gary@jessie17:~$ sudo systemctl status weewx-multi.service
● weewx-multi.service - LSB: weewx-multi
   Loaded: loaded (/etc/init.d/weewx-multi)
   Active: failed (Result: exit-code) since Thu 2017-09-07 09:49:39 AEST; 
17s ago
  Process: 1356 ExecStart=/etc/init.d/weewx-multi start (code=exited, status
=1/FAILURE)

Sep 07 09:49:39 jessie17 weewx-bloomsky[1381]: engine: Loading service weewx
.engine.StdPrint
Sep 07 09:49:39 jessie17 weewx-bloomsky[1381]: engine: Finished loading 
service weewx.engine.StdPrint
Sep 07 09:49:39 jessie17 weewx-bloomsky[1381]: engine: Loading service weewx
.engine.StdReport
Sep 07 09:49:39 jessie17 weewx-bloomsky[1381]: engine: Finished loading 
service weewx.engine.StdReport
Sep 07 09:49:39 jessie17 weewx-bloomsky[1381]: engine: Starting up weewx 
version 3.7.1
Sep 07 09:49:39 jessie17 weewx-bloomsky[1381]: engine: Station does not 
support reading the time
Sep 07 09:49:39 jessie17 weewx-bloomsky[1381]: engine: Starting main packet 
loop.
Sep 07 09:49:40 jessie17 weewx-bloomsky[1381]: bloomsky: bloomsky-client: 
Next update in 15 seconds
Sep 07 09:49:55 jessie17 weewx-bloomsky[1381]: bloomsky: bloomsky-client: 
url: https://api.bloomsky.com/api/skydata/ data: {'unit': 'intl'} hdr: 
{'Authorization': 'qsM='}
Sep 07 09:49:55 jessie17 weewx-bloomsky[1381]: bloomsky: bloomsky-client: 
Next update in 15 seconds
gary@jessie17:~$ sudo journalctl -xn
-- Logs begin at Thu 2017-09-07 08:16:03 AEST, end at Thu 2017-09-07 09:50:
11 AEST. --
Sep 07 09:49:39 jessie17 weewx-bloomsky[1381]: engine: Starting main packet 
loop.
Sep 07 09:49:39 jessie17 sudo[1345]: pam_unix(sudo:session): session closed 
for user root
Sep 07 09:49:40 jessie17 weewx-bloomsky[1381]: bloomsky: bloomsky-client: 
Next update in 15 seconds
Sep 07 09:49:55 jessie17 weewx-bloomsky[1381]: bloomsky: bloomsky-client: 
url: https://api.bloomsky.com/api/skydata/ data: {'unit': 'intl'} hdr: 
{'Authorization': 'qsM='}
Sep 07 09:49:55 jessie17 weewx-bloomsky[1381]: bloomsky: bloomsky-client: 
Next update in 15 seconds
Sep 07 09:49:56 jessie17 sudo[1400]: gary : TTY=pts/0 ; PWD=/home/gary ; 
USER=root ; COMMAND=/bin/systemctl status weewx-multi.service
Sep 07 09:49:56 jessie17 sudo[1400]: pam_unix(sudo:session): session opened 
for user root by gary(uid=0)
Sep 07 09:49:56 jessie17 sudo[1400]: pam_unix(sudo:session): session closed 
for user root
Sep 07 09:50:11 jessie17 sudo[1402]: gary : TTY=pts/0 ; PWD=/home/gary ; 
USER=root ; COMMAND=/bin/journalctl -xn
Sep 07 09:50:11 jessie17 sudo[1402]: pam_unix(sudo:session): session opened 
for user root by gary(uid=0)




On Wednesday, 6 September 2017 17:57:53 UTC+10, pkus...@hs-harz.de wrote:
>
> Hi Gary,
>
> what is the output from
>
> gary@jessie17:~$ sudo systemctl status weewx-multi.service
>
> and
>
> gary@jessie17:~$ sudo journalctl -xn
>
> best regards
>
> Peter
>
>
>
>> gary@jessie17:~$ sudo /etc/init.d/weewx-multi start
>> [] Starting weewx-multi (via systemctl): weewx-multi.serviceJob for 
>> weewx-multi.service failed. See 'systemctl status weewx-multi.service' 
>> and 'journalctl -xn' for details.
>>  failed!
>>
>

[weewx-development] Re: Advice on a new driver and how to make it available

2017-09-06 Thread Francesco Scaramella
Thanks Susan for the prompt correction of the driver and for the indication 
received. In fact I had already known the problems of My network. 
Unfortunately the station is installed in a country location not served by 
ADSL services and we share between neighbors a same connection to be able 
to have a little all... just keep it stable is a big job. anyway I'll 
treasure the indication to bring In RAM the log!! I forgot to do it!! 
Thanks immensely for the help received!