On 29 July 2016 at 00:46, vince wrote:
> Interesting stuff and surprisingly hard to get done completely
[...]
> but having logs up to a minute max
> beforehand was helpful in 95% of the post-mortem cases
Ah, duly noted. More on that later...
[...]
> result was 'really' small in ramdisk - I w
On Thursday, July 28, 2016 at 2:41:48 PM UTC-7, lonehighway wrote:
>
>
>>> You 'sure' the sheeva can't be updated ?. I'm running on a Seagate
>> Dockstar (a sheeva plug with half the memory) using spinning disk in it
>> after editing the bootloader to look there... and it's debian 7.6 and
>> p
>
>
>> You 'sure' the sheeva can't be updated ?. I'm running on a Seagate
> Dockstar (a sheeva plug with half the memory) using spinning disk in it
> after editing the bootloader to look there... and it's debian 7.6 and
> pretty patched up toward current - it's been up 184 days and I don't li
On Thursday, July 28, 2016 at 12:26:55 PM UTC-7, lonehighway wrote:
> Would that make 3.5.0 fail to run? And yes the Sheevaplug is ancient and
> can't be updated, still running deb6, hence I'm moving it to Pidora on a
> Pi. (Pidora has it's own challenges but so far so good!)
>
>
>
>
You 'sure'
If a skin configuration file is missing, the report generator should just
skip it and move on. Certainly, it should not terminate weewx. Looking
through the v3.5 code, I don't see any reason why it wouldn't keep going.
In any case, why not just copy the Rsync directory from the tar file to
/home/w
root@sheevaplug:/home/weewx/skins# ls
Ftp Standard
the 3.5.0 folder I'm trying to install from does have Ftp Rsync Standard.
I've been getting that error for years, always ignored it because as far as
I know I'm not using it.
Jul 28 13:15:26 sheevaplug weewx[773]: reportengine: Cannot re
Interesting stuff and surprisingly hard to get done completely
My job from 2000-2013 was to develop+support a very custom minimized
fedora/centos system that ran totally into ramdisk on a small-memory Intel
box, treating it like an embedded system. Reason was that these systems
'never' had
Oops. I found the 'install' command.
Does /home/weewx/skins/Rsync/skin.conf exist? How about the skin directory
/home/weewx/skins? What are its contents?
It looks like something got messed up in your skin subdirectory...
-tk
On Thu, Jul 28, 2016 at 5:18 AM, Thomas Keffer wrote:
> Did you do
Did you do an "install" after the "build?"
Haven't seen a SheevaPlug in a while!
-tk
On Thu, Jul 28, 2016 at 12:00 AM, lonehighway wrote:
> Here is the log of the build, install, and attempted start, with the tail
> log showing the previous stop and nothing new. I recovered by re-installing
>
NEW_LOOP_PACKET is the data from the hardware - and depending on the
hardware may be either for all the sensors or just some - different
hardware works in different ways. NEW_ARCHIVE_RECORD will be the average
data values for all sensors received during the archive period (often 5
minutes). T
I'm not very into python programming
I found NEW_LOOP_PACKET but seems working with all data within an array
'packet'.
What I need is to get spare data (temp, wind, etc) before composing the
packet...where file I have to look at?
Then I will use other python library to send the data via modbus
Hi,
Have you tried running weewx from the command line?
sudo weewxd weewx.conf
It might give you some info re what is going wrong.
Gary
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails fr
Here is the log of the build, install, and attempted start, with the tail
log showing the previous stop and nothing new. I recovered by re-installing
3.2.1 which worked as expected.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe
13 matches
Mail list logo
