Thanks for the hint:
it might explain why the data-passthrough to WUnderground etc. still OK,
because using this Raspberry with RAM-filingsystem as workarea, not the
SD-card.
Indeed, then urgent need to save/backup all valuable data from this
SD-card [if access still possible]
Op 15-7-2025 om 21:40 schreef 'Peter Fletcher' via weewx-user:
A 'dying' SD will frequently report that all the files on it are
readonly and will not allow new data to be written to it. Arguably,
this is a feature, rather than a bug, since it gives you a chance to
copy wanted data off it before it completely fails.
On Monday, July 14, 2025 at 6:21:54 PM UTC-4 Ton vanN wrote:
Main problem seems corruption of the O.S. resulting that it has
become read-only for all files, not so much corruption of WeeWX.
Example.
input at PuttySSH of CLI = sudo /home/weewx/bin/weewxd
/home/weewx/weewx.conf
yields a 'normal' reaction until writing is required towards the
publichtml-folder, causing an O.S.error
Unfortunately no simple remedy to correct the O.S.
=> solution = setup of fresh, second weewx at other Raspberry to
get new, operational skins etc.
Op donderdag 10 juli 2025 om 21:24:37 UTC+2 schreef Anton
vanNwnhzn@GMail:
Digging deeper, (blankly) observe that reading
Weatherflow_Tempest and output towards CWOP, HWA, Weathercloud
and WUnderground still running without problems.
Reason to keep alive, and study what is still (re)usable.
Op 10-7-2025 om 19:50 schreef vince:
If you can do so, imaging a new SD card and starting over
might be your simplest path forward. Save a copy of your
current weewx.sdb and later use it to catch up your new
installation.
On Thursday, July 10, 2025 at 6:45:18 AM UTC-7 Ton vanN wrote:
Considering age of the installation perhaps appropriate &
easier to make a fresh install on another Raspberry with
fresh SD-card, with recent version of Raspian and with
v5.1 for WeeWX, and make setup /equivalent/ to old one
for the readers and for the outputs.
Pity for loss of data, or exists an easy path to merge
the old/latest sdb in the new WeeWX-install?
Op woensdag 9 juli 2025 om 20:41:16 UTC+2 schreef Ton vanN:
Also weird:
CLI => /var/log $ sudo crontab -e
Report:
/tmp/crontab.spPpVc: Bestandssysteem is alleen-lezen
Creation of temporary crontab file failed - aborting
Op woensdag 9 juli 2025 om 20:37:18 UTC+2 schreef Ton
vanN:
Reran CLI with shown result:
sudo du -sm /var/log
2420 /var/log
Much smaller than in 2023 ......
Op woensdag 9 juli 2025 om 20:30:43 UTC+2 schreef
Ton vanN:
_*Correction/addition*_, see below extract
from PuttySSH-readout on files:
-rwxrwxr-x 1 root adm 805154629 mrt 6
11:47 daemon.log
-rwxrwxr-x 1 root adm 1251904421 mrt 2
00:02 daemon.log.1
-rwxrwxr-x 1 root adm 34392792 feb 23
00:02 daemon.log.2.gz
-rwxrwxr-x 1 root adm 34421901 feb 16
00:02 daemon.log.3.gz
-rwxrwxr-x 1 root adm 34334370 feb 9
00:02 daemon.log.4.gz
-rw-r----- 1 root adm 5318820 mrt 6
11:47 debug
-rw-r----- 1 root adm 8165348 mrt 2
00:01 debug.1
-rw-r----- 1 root adm 286230 feb 23
00:01 debug.2.gz
-rw-r----- 1 root adm 149939 feb 16
00:01 debug.3.gz
-rw-r----- 1 root adm 254542 feb 9
00:01 debug.4.gz
-rw-r--r-- 1 root root 0 mrt 1
00:00 dpkg.log
-rw-r--r-- 1 root root 1850 feb 21
14:04 dpkg.log.1
-rw-r--r-- 1 root root 322 feb 13
22:56 dpkg.log.2.gz
-rw-r--r-- 1 root root 937 nov 7
14:46 dpkg.log.3.gz
-rw-r--r-- 1 root root 7777 jul 27
2024 dpkg.log.4.gz
-rwxrwxr-x 1 root root 1665 jul 27
2024 dpkg.log.5.gz
-rw-r--r-- 1 root root 2784 feb 12
2023 faillog
-rwxrwxr-x 1 root root 2847 dec 4
2022 fontconfig.log
drwxr-xr-x 3 root root 4096 dec 4 2022 hp
-rwxrwxr-x 1 root adm 1954376 mrt 6
11:47 kern.log
-rwxrwxr-x 1 root adm 32165 feb 22
09:36 kern.log.1
-rwxrwxr-x 1 root adm 8440 jan 30
13:02 kern.log.2.gz
-rwxrwxr-x 1 root adm 1178 jan 25
23:23 kern.log.3.gz
-rwxrwxr-x 1 root adm 1237 jan 18
21:54 kern.log.4.gz
-rw-rw-r-- 1 root utmp 292292 mrt 6
11:46 lastlog
drwx--x--x 2 root root 4096 mrt 6
11:46 lightdm
-rw-r----- 1 root adm 3292608 mrt 6
11:47 messages
-rw-r----- 1 root adm 3131508 mrt 2
00:00 messages.1
-rw-r----- 1 root adm 158279 feb 23
00:00 messages.2.gz
-rw-r----- 1 root adm 82455 feb 16
00:00 messages.3.gz
-rw-r----- 1 root adm 137821 feb 9
00:00 messages.4.gz
drwx------ 2 root root 4096 sep 26
2019 private
-rw-r----- 1 root adm 93744258 mrt 6
11:47 syslog
-rw-r----- 1 root adm 182939786 mrt 6
00:01 syslog.1
-rw-r----- 1 root adm 5800444 mrt 5
00:00 syslog.2.gz
-rw-r----- 1 root adm 5804241 mrt 4
00:00 syslog.3.gz
-rw-r----- 1 root adm 5805256 mrt 3
00:00 syslog.4.gz
-rw-r----- 1 root adm 5802534 mrt 2
00:00 syslog.5.gz
-rw-r----- 1 root adm 5817293 mrt 1
00:00 syslog.6.gz
-rw-r----- 1 root adm 5820100 feb 28
00:00 syslog.7.gz
-rwxrwxr-x 1 root adm 13973209 mrt 6
11:47 user.log
-rwxrwxr-x 1 root adm 21557861 mrt 2
00:01 user.log.1
-rwxrwxr-x 1 root adm 832412 feb 23
00:01 user.log.2.gz
-rwxrwxr-x 1 root adm 444514 feb 16
00:01 user.log.3.gz
-rwxrwxr-x 1 root adm 791921 feb 9
00:01 user.log.4.gz
*_In addition_*, since the events of 2023 the
configuration of WeeWX stayed unchanged 4.8.0.
and the O.S.-status is equally unchanged
(although updated&upgraded as far as possible):
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/";
SUPPORT_URL="http://www.raspbian.org/RaspbianForums";
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";
Op woensdag 9 juli 2025 om 20:12:42 UTC+2
schreef Ton vanN:
No root-cause found and therefore
continued with the 'minimized' /var/log
with fingers-crossed.
After almost 2 years must revisit this
topic, because again the subject
raspberry on strike.
Via PuttySSH tried the same remedy as
hinted then, but to no effect.
Changed path to /var/log/
CLI:
sudo rm daemon.log.1
Translated reporting is:
rm: cannot remove ''daemon.log.1' Filing
system is read-only
As remedy tried to change the attributes
of files by issue of
sudo chmod 775 *.*
at several levels, but resulting report
is same:
Filing system is read-only
Weird, because with WinScp and
ls -l
the attributes for all log-files show as
rwxrwsr-x
Any ide what has happened, and how to remedy?
Op woensdag 1 november 2023 om 12:10:26
UTC+1 schreef Ton vanN:
Is surprisingly effective remedy:
all files now significantly smaller
and WeeWX running smoothly.
But 'digging' to find root-cause for
this unpleasant 'growing'.
Op donderdag 19 oktober 2023 om
19:08:55 UTC+2 schreef vince:
Do a "sudo rm daemon.log.1
debug.1 kern.log.1 user.log.1" to
get immediate relief.
Then look at the daemon.log,
debug, kern.log, and user.log
files that remain to see what is
in them. This is very unusual.
You have something in your os
that is logging something you
need to investigate. Even if
you do a "tail -n 20" of each
file it will help you determine
what is happening.
On Thursday, October 19, 2023 at
5:15:18 AM UTC-7 Ton vanN wrote:
*raspberrypi9:~ $ *ls -al
/var/log
-rwxrwxr-x 1 root adm
89212455 okt 19 00:00 auth.log.1
-rwxrwxr-x 1 root adm
113695224 okt 19 14:06
daemon.log
-rwxrwxr-x 1 root adm
23122752257 okt 19 00:00
daemon.log.1
-rw-r----- 1 root adm
2756977 okt 19 14:05 debug
-rw-r----- 1 root adm
1048983611 okt 18 23:55 debug.1
-rwxrwxr-x 1 root adm
13796027 okt 18 20:31 kern.log.1
-rw-r----- 1 root adm
119656811 okt 19 00:00
messages.1
-rw-r----- 1 root adm
196420717 okt 19 00:00 syslog.1
-rwxrwxr-x 1 root adm
3022087 okt 19 14:05 user.log
-rwxrwxr-x 1 root adm
1175652544 okt 18 23:55
user.log.1
--
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 visit
https://groups.google.com/d/msgid/weewx-user/47a4ef1e-1ac9-49b4-aad4-6dd767c858fen%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/47a4ef1e-1ac9-49b4-aad4-6dd767c858fen%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
===============================================================
Contactinfo voor Anton van Nieuwenhuijzen:
Email [email protected]
===============================================================
Deze E-mail en eventuele aanhangende files zijn
alleen bestemd voor de geadresseerde(n).
Als je deze E-mail ten onrechte hebt ontvangen,
dan aub verwijderen en de afzender informeren.
--
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 visit
https://groups.google.com/d/msgid/weewx-user/553843bb-a04c-42a4-84cb-2457dc258b75n%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/553843bb-a04c-42a4-84cb-2457dc258b75n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
===============================================================
Contactinfo voor Anton van Nieuwenhuijzen:
Email [email protected]
===============================================================
Deze E-mail en eventuele aanhangende files zijn
alleen bestemd voor de geadresseerde(n).
Als je deze E-mail ten onrechte hebt ontvangen,
dan aub verwijderen en de afzender informeren.
--
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 visit
https://groups.google.com/d/msgid/weewx-user/c4a4467b-5ee3-413f-bfbf-81404a764b5c%40gmail.com.
