Sorry all of that I already did on old server. Below I did this again, no other logs. This is the reason why I had to reinstall server again and again not working. I run manually again fev times and all what I get in log is
# WEEWX CONFIGURATION FILE # # Copyright (c) 2009-2019 Tom Keffer <[email protected]> # See the file LICENSE.txt for your rights. ############################################################################## # This section is for general configuration information. # Set to 1 for extra debug info, otherwise comment it out or set to zero debug = 1 # Root directory of the weewx data file hierarchy for this station WEEWX_ROOT = / # Whether to log successful operations log_success = True # Whether to log unsuccessful operations log_failure = True # How long to wait before timing out a socket (FTP, HTTP) connection socket_timeout = 20 # Do not modify this. It is used when installing and updating weewx. version = 3.9.1 sudo weewxd /etc/weewx/weewx.conf Jun 14 09:00:23 povej weewx[6760]: engine: Main loop exiting. Shutting engine down. Jun 14 09:00:23 povej weewx[6760]: interceptor: MainThread: shutting down server thread Jun 14 09:00:24 povej weewx[6760]: engine: Keyboard interrupt. Jun 14 09:00:26 povej weewx[11161]: engine: Initializing weewx version 3.9.1 Jun 14 09:00:26 povej weewx[11161]: engine: Using Python 2.7.5 (default, Apr 9 2019, 14:30:50) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] Jun 14 09:00:26 povej weewx[11161]: engine: Platform Linux-3.10.0-957.12.2.el7.x86_64-x86_64-with-centos-7.6.1810-Core Jun 14 09:00:26 povej weewx[11161]: engine: Locale is 'sl_SI.UTF-8' Jun 14 09:00:26 povej weewx[11161]: engine: Using configuration file /etc/weewx/weewx.conf Jun 14 09:00:26 povej weewx[11161]: engine: Loading station type Interceptor (user.interceptor) Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: driver version is 0.45 Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: device type: acurite-bridge Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: sensor map: None Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: mode is listen Jun 14 09:00:26 povej weewx[11161]: interceptor: MainThread: listen on :9900 Jun 14 09:00:26 povej weewx[11161]: engine: StdConvert target unit is 0x1 Jun 14 09:00:26 povej weewx[11161]: wxcalculate: The following values will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, heatindex=prefer_hardware, maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, cloudbase=prefer_hardware Jun 14 09:00:26 povej weewx[11161]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS Jun 14 09:00:26 povej weewx[11161]: engine: Archive will use data binding wx_binding Jun 14 09:00:26 povej weewx[11161]: engine: Record generation will be attempted in 'hardware' Jun 14 09:00:26 povej weewx[11161]: engine: Using archive interval of 60 seconds (specified in weewx configuration) Jun 14 09:00:26 povej weewx[11161]: engine: Using binding 'wx_binding' to database 'weewx' Jun 14 09:00:26 povej weewx[11161]: manager: Starting backfill of daily summaries Jun 14 09:00:26 povej weewx[11161]: restx: StationRegistry: Registration not requested. Jun 14 09:00:26 povej weewx[11161]: restx: Wunderground-PWS: Data for station IDO8 will be posted Jun 14 09:00:26 povej weewx[11161]: restx: PWSweather: Posting not enabled. Jun 14 09:00:26 povej weewx[11161]: restx: CWOP: Posting not enabled. Jun 14 09:00:26 povej weewx[11161]: restx: WOW: Posting not enabled. Jun 14 09:00:26 povej weewx[11161]: restx: AWEKAS: Posting not enabled. Jun 14 09:00:26 povej weewx[11161]: engine: Starting up weewx version 3.9.1 Jun 14 09:00:26 povej weewx[11161]: engine: Starting main packet loop. Dne petek, 14. junij 2019 03.25.32 UTC+2 je oseba Andrew Milner napisala: > > Have you done what Matthew asked some time ago and run weewx manually - > not as a daemon?? > > Did you get any LOOP packets logged to the screen when you ran manually?? > > The log you posted just shows a normal startup - although debug does not > appear to be set. Did you edit the correct weewx,conf file when setting > debug=1?? > > > > On Thursday, 13 June 2019 19:52:46 UTC+3, Damjan Hajsek wrote: >> >> Sorry I already post log from old centos server and it is the same on new >> centos server. All I have in log is only this >> >> Jun 13 18:50:56 povej systemd: Started SYSV: start and stop the weewx >> weather system. >> Jun 13 18:50:56 povej weewx[15848]: engine: Using configuration file >> /etc/weewx/weewx.conf >> Jun 13 18:50:56 povej weewx[15848]: engine: Loading station type >> Interceptor (user.interceptor) >> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: driver >> version is 0.45 >> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: device type: >> acurite-bridge >> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: sensor map: >> None >> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: mode is >> listen >> Jun 13 18:50:56 povej weewx[15848]: interceptor: MainThread: listen on >> :9900 >> Jun 13 18:50:56 povej weewx[15848]: engine: StdConvert target unit is 0x1 >> Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following values >> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, >> dewpoint=prefer_hardware, appTemp=prefer_hardware, >> rainRate=prefer_hardware, windrun=prefer_hardware, >> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, >> humidex=prefer_hardware, pressure=prefer_hardware, >> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, >> cloudbase=prefer_hardware >> Jun 13 18:50:56 povej weewx[15848]: wxcalculate: The following algorithms >> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS >> Jun 13 18:50:56 povej weewx[15848]: engine: Archive will use data binding >> wx_binding >> Jun 13 18:50:56 povej weewx[15848]: engine: Record generation will be >> attempted in 'hardware' >> Jun 13 18:50:56 povej weewx[15848]: engine: Using archive interval of 60 >> seconds (specified in weewx configuration) >> Jun 13 18:50:56 povej weewx[15848]: engine: Using binding 'wx_binding' to >> database 'weewx' >> Jun 13 18:50:56 povej weewx[15848]: manager: Starting backfill of daily >> summaries >> Jun 13 18:50:56 povej weewx[15848]: restx: StationRegistry: Registration >> not requested. >> Jun 13 18:50:56 povej weewx[15848]: restx: Wunderground-PWS: Data for >> station IDOE7 will be posted >> Jun 13 18:50:56 povej weewx[15848]: restx: PWSweather: Posting not >> enabled. >> Jun 13 18:50:56 povej weewx[15848]: restx: CWOP: Posting not enabled. >> Jun 13 18:50:56 povej weewx[15848]: restx: WOW: Posting not enabled. >> Jun 13 18:50:56 povej weewx[15848]: restx: AWEKAS: Posting not enabled. >> Jun 13 18:50:56 povej weewx[15848]: engine: Starting up weewx version >> 3.9.1 >> Jun 13 18:50:56 povej weewx[15848]: engine: Starting main packet loop. >> >> Dne četrtek, 13. junij 2019 14.02.25 UTC+2 je oseba Andrew Milner >> napisala: >>> >>> what does weex say in the log when it is starting?? weewx outputs a lot >>> of information at startup - so you need to locate the log and post the log >>> to this forum then we may be able to help you further >>> >>> >>> >>> On Thursday, 13 June 2019 11:11:32 UTC+3, Damjan Hajsek wrote: >>>> >>>> Any idea how to solve this please? >>>> >>>> Dne torek, 11. junij 2019 22.24.35 UTC+2 je oseba Damjan Hajsek >>>> napisala: >>>>> >>>>> I have installed fresh new server centos 7.6 >>>>> also installed fresh installation of weewx 3.9.1 >>>>> also installed driver interceptor. >>>>> And I get the same result as before. >>>>> I have checked database doesn't change or fill up. >>>>> there is no loop of weewx in logs and debug is 1 >>>>> >>>>> >>>>> sudo strace -d /tmp/weewxd_strace.txt weewxd >>>>> strace: ptrace_setoptions = 0x11 >>>>> strace: new tcb for pid 11807, active tcbs:1 >>>>> strace: [wait(0x80137f) = 11807] WIFSTOPPED,sig=SIGSTOP,EVENT_STOP >>>>> (128) >>>>> strace: pid 11807 has TCB_STARTUP, initializing it >>>>> strace: [wait(0x80057f) = 11807] WIFSTOPPED,sig=SIGTRAP,EVENT_STOP >>>>> (128) >>>>> strace: [wait(0x00127f) = 11807] WIFSTOPPED,sig=SIGCONT >>>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133 >>>>> execve("/tmp/weewxd_strace.txt", ["/tmp/weewxd_strace.txt", "weewxd"], >>>>> [/* 18 vars */]strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133 >>>>> ) = -1 ENOEXEC (Exec format error) >>>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133 >>>>> write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec >>>>> format error >>>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133 >>>>> ) = 32 >>>>> strace: [wait(0x00857f) = 11807] WIFSTOPPED,sig=133 >>>>> exit_group(1) = ? >>>>> strace: [wait(0x000100) = 11807] WIFEXITED,exitcode=1 >>>>> +++ exited with 1 +++ >>>>> strace: dropped tcb for pid 11807, 0 remain >>>>> >>>>> >>>>> >>>>> Dne četrtek, 25. april 2019 18.38.58 UTC+2 je oseba Leon Shaner >>>>> napisala: >>>>>> >>>>>> Damian, >>>>>> >>>>>> Still very strange that we do not see debug = 1 echoed in the logs. >>>>>> >>>>>> At this point I am at a loss other than, perhaps you could preface >>>>>> the command with strace so we can see what is going on. I expect it >>>>>> gets >>>>>> to a point where it is just more or less sleeping, doing nothing. >>>>>> >>>>>> I say that based on your previous "ps -elf" output where it showed >>>>>> 00:00:00 cpu time and was sleeping. It is normal for the process to >>>>>> sleep >>>>>> when there is no input, but it should have to be doing at least some >>>>>> work >>>>>> from time to time. >>>>>> >>>>>> From the ps man page: >>>>>> >>>>>> PROCESS STATE CODES >>>>>> Here are the different values that the s, stat and state >>>>>> output specifiers (header "STAT" or "S") will display to describe the >>>>>> state >>>>>> of a process: >>>>>> >>>>>> D uninterruptible sleep (usually IO) >>>>>> R running or runnable (on run queue) >>>>>> S interruptible sleep (waiting for an event to >>>>>> complete) >>>>>> T stopped by job control signal >>>>>> t stopped by debugger during the tracing >>>>>> W paging (not valid since the 2.6.xx kernel) >>>>>> X dead (should never be seen) >>>>>> Z defunct ("zombie") process, terminated but not >>>>>> reaped by its parent >>>>>> >>>>>> Here is an example of how to strace the process and get the debug >>>>>> output into a file: >>>>>> >>>>>> $ sudo strace -o /tmp/weewxd_strace.txt weewxd >>>>>> >>>>>> You can "tail -f /tmp/weewxd_strace.txt" to see what is going on. >>>>>> It will likely get to a point where it is quiet for long periods. >>>>>> You can stop the strace after you see those a couple of times. >>>>>> >>>>>> The output could be quite large so you may want to compress it: >>>>>> >>>>>> $ gzip /tmp/weewxd_strace.txt >>>>>> >>>>>> Regards, >>>>>> Leon >>>>>> -- >>>>>> Leon Shaner :: Dearborn, Michigan (iPad Pro) >>>>>> >>>>>> On Apr 25, 2019, at 10:30 AM, Damjan Hajsek <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Hi >>>>>> I have done this and it is all the same. I created some logs from >>>>>> manually starting weewx. >>>>>> when I start weewx manually sudo weewxd /etc/weewx/weewx.conf' >>>>>> it didn't crash, I stopped it. >>>>>> here it is. >>>>>> >>>>>> http://zerobin.povej.net/?b06b1ad942bc51a2#34Nj1ed+8odSg7jHbjz7AU+WsqZ3yxPjZDB1EPHyVAk= >>>>>> >>>>>> >>>>>> >>>>>> Dne sreda, 24. april 2019 15.48.25 UTC+2 je oseba Leon Shaner >>>>>> napisala: >>>>>>> >>>>>>> Damian, >>>>>>> You have to give wee_config a command. >>>>>>> From the usage, you want this: >>>>>>> >>>>>>> $ sudo wee_config --reconfigure --config=/etc/weewx/weewx.conf >>>>>>> >>>>>>> (Although you can leave the --config part off, since your conf file >>>>>>> is located in the default location). >>>>>>> >>>>>>> But do be sure to back up the config file first... >>>>>>> >>>>>>> Regards, >>>>>>> Leon >>>>>>> -- >>>>>>> Leon Shaner :: Dearborn, Michigan (iPad Pro) >>>>>>> >>>>>>> On Apr 24, 2019, at 6:20 AM, Damjan Hajsek <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> Hi >>>>>>> What I did is first use some old weewx.conf file from last year and >>>>>>> doesn't work either. >>>>>>> So I tried to reconfigure it but can't >>>>>>> when I run wee_config --help I get list of help >>>>>>> but when I do this I get >>>>>>> wee_config /etc/weewx/weewx.conf >>>>>>> No command specified. >>>>>>> wee_config --config=/etc/weewx/weewx.conf >>>>>>> No command specified. >>>>>>> >>>>>>> >>>>>>> Dne torek, 23. april 2019 15.17.24 UTC+2 je oseba Leon Shaner >>>>>>> napisala: >>>>>>>> >>>>>>>> Damian, >>>>>>>> >>>>>>>> These logs still do not state debug = 1. >>>>>>>> It still could be that the weewx.conf isn't being parsed correctly, >>>>>>>> and isn't even able to read the debug = 1 setting. >>>>>>>> >>>>>>>> Did you try my suggestions for how to "rebuild" the conf file? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Leon >>>>>>>> -- >>>>>>>> Leon Shaner :: Dearborn, Michigan (iPhone) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Apr 23, 2019, at 8:45 AM, Damjan Hajsek <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Hi >>>>>>>> I have followed your instruction so I did all as described >>>>>>>> first turn off monit >>>>>>>> stop weewx >>>>>>>> debug = 1 was already set >>>>>>>> than I run weewx manually >>>>>>>> here is a log from that >>>>>>>> >>>>>>>> >>>>>>>> http://zerobin.povej.net/?a63b7ac09e222bcc#9Y5+B9WWtxXgUJWTKZWmzElusp9QRgEK5Pde606SvQc= >>>>>>>> >>>>>>>> >>>>>>>> http://zerobin.povej.net/?7d382c267025fd54#0p/b4Z0y5k7U3qFc8T/2Sgl0CbbU8ZkYxdSFCRh/I4I= >>>>>>>> >>>>>>>> >>>>>>>> Dne nedelja, 21. april 2019 15.41.04 UTC+2 je oseba mwall napisala: >>>>>>>>> >>>>>>>>> at this point in the thread it is not clear what is happening or >>>>>>>>> what is the state of your system. >>>>>>>>> >>>>>>>>> so start over and explain what your configuration looks like now >>>>>>>>> >>>>>>>>> then, to diagnose weewx, do the following: >>>>>>>>> >>>>>>>>> - remove whatever it is that keeps restarting weewx >>>>>>>>> - stop weewx if it is running >>>>>>>>> - set debug=1 in your weewx configuration >>>>>>>>> - run weewx directly, not as a daemon >>>>>>>>> - if weewx crashes, post (1) the log prior to the crash, (2) the >>>>>>>>> stack trace or other output from the console in which you started it >>>>>>>>> >>>>>>>>> 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]. >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>>> -- >>>>>>> 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]. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>>> -- >>>>>> 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]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>>> -- 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/2c9d8ccb-3de8-41e1-bf06-dd28620a40a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
