Re: [weewx-user] Upgraded to V5 - will not run automaticly

[vince]

yup - overloaded terminology.  Sounds a little like running a process under 
cgroups isolation 15+ years ago.  Looking that up briefly I see the term 
'process container' which I guess is the same thing.  Thanks.

On Thursday, May 9, 2024 at 6:21:16 AM UTC-7 Paul R Anderson wrote:

> Vince,
> Your confusion is probably caused by the enormous popularity of Docker. At 
> this point most of us hear the word Container and only think of Docker. 
> This is also a huge reason why LXC Containers are nowhere near as popular 
> as Docker containers , no one knows they exist, let alone what they are.  
> *LXC Containers are system containers*
> *Docker Containers are Application containers*
> There are generally at least two types of containers: Application 
> containers, and System containers
> There's a good blog post from Ubuntu that explains it much better than I 
> can.
> What are Linux containers? 
> 
>
> Brief excerpt from the blog post:
>
> " Application vs system containers
> Application containers (such as Docker) are containers running a single 
> process per container. They run stateless types of workloads so that you 
> can ramp up and down as needed – create new containers and delete them at 
> any time. Usually, you don’t need to care about the lifecycle of those 
> containers, as they are meant to be ephemeral.
>
> The other type of containers, system containers, are much closer to a 
> virtual or a physical machine. They run a full operating system inside 
> them, and you manage them exactly as you would a virtual or a physical 
> machine. That means you can install packages inside them, you can manage 
> services, define backup policies, monitoring, and all other aspects as you 
> usually would with a virtual machine. These containers are usually very 
> long-lasting. If you need to update them, you can do so with the normal 
> tooling of the Linux distribution you are using. It also means that you 
> will get normal security updates from distributions for those containers, 
> so you wouldn’t need to wait for any image to be published to get the 
> security fixes. "
>
>
>
> Paul
>
> On Wed, May 8, 2024 at 8:10 PM vince  wrote:
>
>> I have to admit being a little confused.  A container running multiple 
>> processes that you can ssh into isn't a container, it's a virtual machine.
>>
>> On Wednesday, May 8, 2024 at 4:42:00 AM UTC-7 Graham Eddy wrote:
>>
>>> i suggest testing before publishing..
>>> that won’t work without the permissions towards end of my lxc/105.conf 
>>> file
>>> *⊣GE⊢*
>>>
>>> On 8 May 2024, at 9:25 PM, G7LTT  wrote:
>>>
>>> Updated to add USB device to the container.
>>>
>>>
>>> -- 
>> 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 weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/dd2f4126-94ec-4456-b7c1-fc0fce4a6d3an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a3740533-b43c-4a87-a879-b50fb2f70aaan%40googlegroups.com.

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[Paul R Anderson]

Vince,
Your confusion is probably caused by the enormous popularity of Docker. At
this point most of us hear the word Container and only think of Docker.
This is also a huge reason why LXC Containers are nowhere near as popular
as Docker containers , no one knows they exist, let alone what they are.
*LXC Containers are system containers*
*Docker Containers are Application containers*
There are generally at least two types of containers: Application
containers, and System containers
There's a good blog post from Ubuntu that explains it much better than I
can.
What are Linux containers?


Brief excerpt from the blog post:

" Application vs system containers
Application containers (such as Docker) are containers running a single
process per container. They run stateless types of workloads so that you
can ramp up and down as needed – create new containers and delete them at
any time. Usually, you don’t need to care about the lifecycle of those
containers, as they are meant to be ephemeral.

The other type of containers, system containers, are much closer to a
virtual or a physical machine. They run a full operating system inside
them, and you manage them exactly as you would a virtual or a physical
machine. That means you can install packages inside them, you can manage
services, define backup policies, monitoring, and all other aspects as you
usually would with a virtual machine. These containers are usually very
long-lasting. If you need to update them, you can do so with the normal
tooling of the Linux distribution you are using. It also means that you
will get normal security updates from distributions for those containers,
so you wouldn’t need to wait for any image to be published to get the
security fixes. "



Paul

On Wed, May 8, 2024 at 8:10 PM vince  wrote:

> I have to admit being a little confused.  A container running multiple
> processes that you can ssh into isn't a container, it's a virtual machine.
>
> On Wednesday, May 8, 2024 at 4:42:00 AM UTC-7 Graham Eddy wrote:
>
>> i suggest testing before publishing..
>> that won’t work without the permissions towards end of my lxc/105.conf
>> file
>> *⊣GE⊢*
>>
>> On 8 May 2024, at 9:25 PM, G7LTT  wrote:
>>
>> Updated to add USB device to the container.
>>
>>
>> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/dd2f4126-94ec-4456-b7c1-fc0fce4a6d3an%40googlegroups.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAOAVAefo5H3zdsacvrtZkvLFxkkD-eAzmpTCKX8hprUpOxzNYg%40mail.gmail.com.

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[Graham Eddy]

probably terminology. an LXC ‘container' is not the same as a docker 
‘container'.
as i understand it, a docker container is a functional blob dropped onto a 
machine that talks to the machine through docker API.
an LXC container, on the other hand, is just a slice of the operating system 
namespace, all the slices sitting side by side as peers.
a VM is more like a docker container where the functional blob is a processor 
emulator, with a low-level API to hardware abstraction.
an LXC container and a VM, both being "mini machines", are usually provisioned 
with network interfaces etc otherwise they aren’t much use.
proxmox supports LXC containers and VMs, either of which could run docker 
inside.
the precise details don't matter here.
cheers
⊣GE⊢

> On 9 May 2024, at 10:10 AM, vince  wrote:
> 
> I have to admit being a little confused.  A container running multiple 
> processes that you can ssh into isn't a container, it's a virtual machine.
> 
> On Wednesday, May 8, 2024 at 4:42:00 AM UTC-7 Graham Eddy wrote:
>> i suggest testing before publishing..
>> that won’t work without the permissions towards end of my lxc/105.conf file
>> ⊣GE⊢
>> 
>>> On 8 May 2024, at 9:25 PM, G7LTT > wrote:
>>> 
>>> Updated to add USB device to the container.
>> 
> 
> 
> -- 
> 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 weewx-user+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/dd2f4126-94ec-4456-b7c1-fc0fce4a6d3an%40googlegroups.com
>  
> .

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6DA6EAAC-CC31-4CCE-AA14-E84480856207%40geddy.au.

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[vince]

I have to admit being a little confused.  A container running multiple 
processes that you can ssh into isn't a container, it's a virtual machine.

On Wednesday, May 8, 2024 at 4:42:00 AM UTC-7 Graham Eddy wrote:

> i suggest testing before publishing..
> that won’t work without the permissions towards end of my lxc/105.conf file
> *⊣GE⊢*
>
> On 8 May 2024, at 9:25 PM, G7LTT  wrote:
>
> Updated to add USB device to the container.
>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/dd2f4126-94ec-4456-b7c1-fc0fce4a6d3an%40googlegroups.com.

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[Graham Eddy]

i suggest testing before publishing..
that won’t work without the permissions towards end of my lxc/105.conf file
⊣GE⊢

> On 8 May 2024, at 9:25 PM, G7LTT  wrote:
> 
> Updated to add USB device to the container.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/18DAED57-21D5-4332-A8A9-AF1FEFEA57C2%40geddy.au.

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[G7LTT]

Ah. I see. You are USB based in your hardware. I did not think of that. I 
run an Ambient WS2000 so the API tool calls out to the Ambient web site and 
sucks back my data (which the display unit has kindly uploaded). I'll add 
an "add a USB port" section

On Wednesday, May 8, 2024 at 12:11:27 AM UTC-4 Graham Eddy wrote:

> proxmox - looking from inside the wx container mentioned in previous 
> email.
> (note that i am running satellite mailer daemon in the container too.)
>
> (venv) *graham@wx*:*~*$ ps -ef
>
> UID  PIDPPID  C STIME TTY  TIME CMD
>
> root   1   0  0 Feb20 ?00:00:31 /lib/systemd/systemd 
> --syste
>
> root  48   1  0 Feb20 ?00:36:34 
> /lib/systemd/systemd-journal
>
> root  99   1  0 Feb20 ?00:00:00 dhclient -4 -v -i -pf 
> /run/d
>
> systemd+ 103   1  0 Feb20 ?00:00:05 
> /lib/systemd/systemd-network
>
> root 132   1  0 Feb20 ?00:00:08 /usr/sbin/cron -f
>
> message+ 133   1  0 Feb20 ?00:00:04 /usr/bin/dbus-daemon 
> --syste
>
> root 139   1  0 Feb20 ?00:00:07 
> /lib/systemd/systemd-logind
>
> root 163   1  0 Feb20 pts/000:00:00 /sbin/agetty -o -p -- 
> \u --n
>
> root 164   1  0 Feb20 pts/100:00:00 /sbin/agetty -o -p -- 
> \u --n
>
> root 165   1  0 Feb20 pts/200:00:00 /sbin/agetty -o -p -- 
> \u --n
>
> root 216   1  0 Feb20 ?00:00:00 sshd: /usr/sbin/sshd 
> -D [lis
>
> root 309   1  0 Feb20 ?00:00:17 
> /usr/lib/postfix/sbin/master
>
> weewx 154403   1  1 Apr09 ?07:00:53 
> /home/weewx/venv/bin/python3
>
> weewx 154443   1  1 Apr09 ?07:00:10 
> /home/weewx/venv/bin/python3
>
> weewx 233257   1  1 May04 ?01:27:47 
> /home/weewx/venv/bin/python3
>
> postfix   246511 309  0 04:02 ?00:00:00 qmgr -l -t unix -u
>
> postfix   248348 309  0 12:19 ?00:00:00 pickup -l -t unix -u -c
>
> root  248664 216  0 13:45 ?00:00:00 sshd: graham [priv]
>
> graham248668   1  0 13:45 ?00:00:00 /lib/systemd/systemd 
> --user
>
> graham248669  248668  0 13:45 ?00:00:00 (sd-pam)
>
> graham248678  248664  0 13:45 ?00:00:00 sshd: graham@pts/3
>
> graham248679  248678  0 13:45 pts/300:00:00 -bash
>
> graham248682  248679  0 13:45 pts/300:00:00 ps -ef
>
>
> (venv) *graham@wx*:*~*$ ls -l /dev
>
> total 0
>
> crw-rw 1 nobody dialout 188, 0 Feb 20 00:38 *aqua*
>
> crwx-- 1 root   tty 136, 0 May  4 10:50 *console*
>
> lrwxrwxrwx 1 root   root11 Feb 20 00:40 *core* -> /proc/kcore
>
> lrwxrwxrwx 1 root   root13 Feb 20 00:40 *fd* -> */proc/self/fd*
>
> crw-rw-rw- 1 nobody nogroup   1, 7 Feb 20 00:38 *full*
>
> lrwxrwxrwx 1 root   root12 Feb 20 00:41 *initctl* -> /run/initctl
>
> lrwxrwxrwx 1 root   root28 Feb 20 00:41 *log* -> 
> */run/systemd/journal/dev-log*
>
> drwxrwxrwt 2 nobody nogroup 40 Feb 20 00:40 mqueue
>
> crw-rw-rw- 1 nobody nogroup   1, 3 Feb 20 00:38 *null*
>
> crw-rw-rw- 1 root   root  5, 2 May  8 13:54 *ptmx*
>
> drwxr-xr-x 2 root   root 0 Feb 20 00:40 *pts*
>
> crw-rw-rw- 1 nobody nogroup   1, 8 Feb 20 00:38 *random*
>
> drwxrwxrwt 2 root   root40 Feb 20 00:40 shm
>
> lrwxrwxrwx 1 root   root15 Feb 20 00:40 *stderr* -> 
> */proc/self/fd/2*
>
> lrwxrwxrwx 1 root   root15 Feb 20 00:40 *stdin* -> 
> */proc/self/fd/0*
>
> lrwxrwxrwx 1 root   root15 Feb 20 00:40 *stdout* -> 
> */proc/self/fd/1*
>
> crw-rw-rw- 1 nobody nogroup   5, 0 May  8 12:00 *tty*
>
> crw--w 1 root   tty 136, 1 Feb 20 00:41 *tty1*
>
> crw--w 1 root   tty 136, 2 Feb 20 00:41 *tty2*
>
> crw-rw-rw- 1 nobody nogroup   1, 9 Feb 20 00:38 *urandom*
>
> crw-rw 1 nobody dialout 188, 1 May  8 13:50 *vp2*
>
> crw-rw-rw- 1 nobody nogroup   1, 5 Feb 20 00:38 *zero*
>
>
> and there is no hint i am running 10 other containers beside it.
>
> i should have mentioned earlier that the memory specified for a container 
> is the *max* allowed - it actually consumes only as much as it needs 
> (with the kernel image being shared). even with all those other containers 
> running, let alone the host’s own requirements, right now the host's 
> resources are hardly used:
>
> *graham@ballina*:*~*$ free -m
>
>totalusedfree  shared  buff/cache   
> available
>
> Mem:78091853 546  115748  
>   5956
>
> Swap:   7807 5167291
>
> *graham@ballina*:*~*$ uptime
>
>  14:04:35 up 78 days, 14:26,  1 user,  load average: 0.00, 0.04, 0.10
>
>
> cheers
> *⊣GE⊢*
>
> On 8 May 2024, at 1:30 PM, Graham Eddy  wrote:
>
> as the doc hinted, putting proxmox itself aside, install/run weewx in LXC 
> *unprivileged* container is the same as running it outside a container, 
> with the benefit of it not

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[Graham Eddy]

proxmox - looking from inside the wx container mentioned in previous email.
(note that i am running satellite mailer daemon in the container too.)

(venv) graham@wx:~$ ps -ef
UID  PIDPPID  C STIME TTY  TIME CMD
root   1   0  0 Feb20 ?00:00:31 /lib/systemd/systemd --syste
root  48   1  0 Feb20 ?00:36:34 /lib/systemd/systemd-journal
root  99   1  0 Feb20 ?00:00:00 dhclient -4 -v -i -pf /run/d
systemd+ 103   1  0 Feb20 ?00:00:05 /lib/systemd/systemd-network
root 132   1  0 Feb20 ?00:00:08 /usr/sbin/cron -f
message+ 133   1  0 Feb20 ?00:00:04 /usr/bin/dbus-daemon --syste
root 139   1  0 Feb20 ?00:00:07 /lib/systemd/systemd-logind
root 163   1  0 Feb20 pts/000:00:00 /sbin/agetty -o -p -- \u --n
root 164   1  0 Feb20 pts/100:00:00 /sbin/agetty -o -p -- \u --n
root 165   1  0 Feb20 pts/200:00:00 /sbin/agetty -o -p -- \u --n
root 216   1  0 Feb20 ?00:00:00 sshd: /usr/sbin/sshd -D [lis
root 309   1  0 Feb20 ?00:00:17 /usr/lib/postfix/sbin/master
weewx 154403   1  1 Apr09 ?07:00:53 /home/weewx/venv/bin/python3
weewx 154443   1  1 Apr09 ?07:00:10 /home/weewx/venv/bin/python3
weewx 233257   1  1 May04 ?01:27:47 /home/weewx/venv/bin/python3
postfix   246511 309  0 04:02 ?00:00:00 qmgr -l -t unix -u
postfix   248348 309  0 12:19 ?00:00:00 pickup -l -t unix -u -c
root  248664 216  0 13:45 ?00:00:00 sshd: graham [priv]
graham248668   1  0 13:45 ?00:00:00 /lib/systemd/systemd --user
graham248669  248668  0 13:45 ?00:00:00 (sd-pam)
graham248678  248664  0 13:45 ?00:00:00 sshd: graham@pts/3
graham248679  248678  0 13:45 pts/300:00:00 -bash
graham248682  248679  0 13:45 pts/300:00:00 ps -ef

(venv) graham@wx:~$ ls -l /dev
total 0
crw-rw 1 nobody dialout 188, 0 Feb 20 00:38 aqua
crwx-- 1 root   tty 136, 0 May  4 10:50 console
lrwxrwxrwx 1 root   root11 Feb 20 00:40 core -> /proc/kcore
lrwxrwxrwx 1 root   root13 Feb 20 00:40 fd -> /proc/self/fd
crw-rw-rw- 1 nobody nogroup   1, 7 Feb 20 00:38 full
lrwxrwxrwx 1 root   root12 Feb 20 00:41 initctl -> /run/initctl
lrwxrwxrwx 1 root   root28 Feb 20 00:41 log -> 
/run/systemd/journal/dev-log
drwxrwxrwt 2 nobody nogroup 40 Feb 20 00:40 mqueue
crw-rw-rw- 1 nobody nogroup   1, 3 Feb 20 00:38 null
crw-rw-rw- 1 root   root  5, 2 May  8 13:54 ptmx
drwxr-xr-x 2 root   root 0 Feb 20 00:40 pts
crw-rw-rw- 1 nobody nogroup   1, 8 Feb 20 00:38 random
drwxrwxrwt 2 root   root40 Feb 20 00:40 shm
lrwxrwxrwx 1 root   root15 Feb 20 00:40 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root   root15 Feb 20 00:40 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root   root15 Feb 20 00:40 stdout -> /proc/self/fd/1
crw-rw-rw- 1 nobody nogroup   5, 0 May  8 12:00 tty
crw--w 1 root   tty 136, 1 Feb 20 00:41 tty1
crw--w 1 root   tty 136, 2 Feb 20 00:41 tty2
crw-rw-rw- 1 nobody nogroup   1, 9 Feb 20 00:38 urandom
crw-rw 1 nobody dialout 188, 1 May  8 13:50 vp2
crw-rw-rw- 1 nobody nogroup   1, 5 Feb 20 00:38 zero

and there is no hint i am running 10 other containers beside it.

i should have mentioned earlier that the memory specified for a container is 
the max allowed - it actually consumes only as much as it needs (with the 
kernel image being shared). even with all those other containers running, let 
alone the host’s own requirements, right now the host's resources are hardly 
used:
graham@ballina:~$ free -m
   totalusedfree  shared  buff/cache   available
Mem:78091853 546  1157485956
Swap:   7807 5167291
graham@ballina:~$ uptime
 14:04:35 up 78 days, 14:26,  1 user,  load average: 0.00, 0.04, 0.10

cheers
⊣GE⊢

> On 8 May 2024, at 1:30 PM, Graham Eddy  wrote:
> 
> as the doc hinted, putting proxmox itself aside, install/run weewx in LXC 
> unprivileged container is the same as running it outside a container, with 
> the benefit of it not being able to trample on rest of host

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/D6EF3005-E040-4770-9D48-2B4476F59A5C%40geddy.au.

Re: [weewx-user] Upgraded to V5 - will not run automaticly

[Graham Eddy]

as the doc hinted, putting proxmox itself aside, install/run weewx in LXC 
unprivileged container is the same as running it outside a container, with the 
benefit of it not being able to trample on rest of host

the tricky parts are where the container walls are visible, the two principal 
cases being
 * direct access to a device file
 * mapping uid/gid inside container to outside

i run a number of unprivileged containers on proxmox server ballina, each with 
their own IP addresses, including ns1 running dnsmasq, broker running mosquitto 
and wx running weewx.
wx runs several instances (stations) of weewx, all sharing same venv. the weewx 
station vantage is, you guessed it, a vp2 running off usb/serial port, so we 
have a device file. the host device file has to be mapped into the container as 
a device file.
(note that i use usual weewx pattern - user weewx in group dialout, device file 
group-owned by dialout)

some proxmox magic i should mention for the config below to make sense: a 
uid/gid of nnn inside a container appears as 100,000+nnn on host outside 
container

graham@ballina:~$ cat /etc/udev/rules.d/99-usb-serial.rules 
#99-usb-serial.rules


# two serial ports on one USB FTDI adapter.
# owned by 'wx' container wherein:
#   * wx.dialout is gid 100020

SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", 
GROUP="100020", MODE="0660"
#not required to distinguish ports##

graham@ballina:~$ sudo cat /etc/pve/lxc/105.conf
#weewx server
#
#| mappings | host view   | container view  |
#| %3A--- | %3A---| %3A---|
#| tty  | /dev/ttyUSB0 660 - (100020) | /dev/aqua 660 - dialout(20) |
#| tty  | /dev/ttyUSB1 660 - (100020) | /dev/vp2 660 - dialout(20)  |
arch: amd64
cores: 1
features: nesting=1
hostname: wx
memory: 512
net0: 
name=eth0,bridge=vmbr0,firewall=1,hwaddr=b2:8d:88:67:d1:bf,ip=dhcp,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-105-disk-0,size=8G
swap: 512
unprivileged: 1
lxc.cgroup2.devices.allow: c 188:* rwm
lxc.mount.entry: /dev/ttyUSB0 dev/aqua none bind,optional,create=file
lxc.mount.entry: /dev/ttyUSB1 dev/vp2 none bind,optional,create=file

the last few lines of the container config file are too advanced for the 
helpful proxmox GUI so need to be added by hand.
user weewx in container wx sees device /dev/vp2

proxmox is excellent for partitioning a host into many servers and minimising 
“breakouts”. containers are extremely resource efficient (e.g. share host’s 
kernel image). virtual machines are also supported but they are resource 
monsters.
last time i checked, proxmox on RPi is unstable - do not use RPi as the metal. 
i am using an apple mac mini from 2012, no hardware add-ons.
cheers
⊣GE⊢

> On 8 May 2024, at 10:25 AM, G7LTT  wrote:
> 
> A start to finish writeup for building a LXC setup would be a nice thing if 
> you have time

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/43C9238F-7909-473C-B29A-3B4E735316D3%40geddy.au.

[weewx-user] Upgraded to V5 - will not run automaticly

[G7LTT]

So I upgraded to V5.0.4 from 4.whatever and it looked like everything went 
ok. But then about an hour later I noticed that the web pages were not 
being updated.  Off to the logs I go - nothing in the logs.

Hmmnnn. OK, time to run it manually at the command line to see if it spews 
anything out. Nope, works perfectly. I can leave "weewxd" running for hours 
without any error. And the pages get updated/uploaded etc etc etc. What 
gives?

I am running Weewx in an LXC container on Proxmox in my homelab system. I 
have the Ambient WS2000 API installed (rather than talk to the station it 
collects the station data from Ambient themselves). 

V4 was running as expected in daemon mode. It would survive a 
reboot/restart of the machine and the container. V5? Not so much. But there 
are no entries in the log files for it which is making me suspicious.

Any ideas?

  

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/124b46ac-97af-4d14-9c2e-86f4b90a6ee1n%40googlegroups.com.