Page 1 of 4
docker cutils recent release not updating
Posted: Thu 12 Sep 2024 2:14 am
by Nossie
Here we go Hans,
thanks
HansR wrote: ↑Thu 12 Sep 2024 1:55 am
Hi Ian,
`
I suggest you create a new topic yourself, no need to split this.
I understand what you are doing but the logfile is from the from the ExtraSensors run. It surprises me that you have to run all separately and that the footer does not update (which means the index.html from the website run does not generate or upload).
Could you do the
Code: Select all
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll website
and post that logfile?
Thanks.
as an FYI - this is what I normally do to run a manual update, but I was trying to see if something was sticking - no change though
Code: Select all
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll website
sleep 10
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll useraskeddata
sleep 10
sudo docker exec -i MXWeather dotnet utils/bin/cumulusutils.dll sysinfo
Re: docker cutils recent release not updating
Posted: Thu 12 Sep 2024 2:19 am
by Nossie
Just noticed this ... will look at it tomorrow
Code: Select all
2024-09-12 03:15:18.205 Verbose 09/12/2024 03:15:182024-09-12 03:15:18.437 Error PhpInit: Error - Resource temporarily unavailable (stewartonweather.com:80)
2024-09-12 03:15:18.438 Error UploadFile: Nothing uploaded because of connection error.
2024-09-12 03:15:18.441 Testing PHP upload compression on http://stewartonweather.com/upload.php
2024-09-12 03:15:34.452 Error PhpInit: Error - Resource temporarily unavailable (stewartonweather.com:80)
2024-09-12 03:15:34.453 Error UploadFile: Nothing uploaded because of connection error.
2024-09-12 03:15:34.453 All done, Entering the finally section...; Closing down.
Re: docker cutils recent release not updating
Posted: Thu 12 Sep 2024 5:57 am
by HansR
It is not only that, it still is the diary MySQL error:
Code: Select all
2024-09-12 03:12:23.912 Information Diary constructor: starting
2024-09-12 03:12:23.937 Error Exception Unknown : The type initializer for 'Microsoft.Data.Sqlite.SqliteConnection' threw an exception.
2024-09-12 03:12:23.939 Error Data (cont): Microsoft.Data.Sqlite
2024-09-12 03:12:23.975 Error Data: at Microsoft.Data.Sqlite.SqliteConnection..ctor(String connectionString)
at CumulusUtils.Diary.GetDiaryDatabase() in C:\Users\hansr\Documents\GitHub\CutilsFramework\CUtilsNET8\Diary.cs:line 99
at CumulusUtils.Diary..ctor(CuSupport s) in C:\Users\hansr\Documents\GitHub\CutilsFramework\CUtilsNET8\Diary.cs:line 61
at CumulusUtils.CUtils.RealMainAsync(String[] args) in C:\Users\hansr\Documents\GitHub\CutilsFramework\CUtilsNET8\Main.cs:line 609
at CumulusUtils.CUtils.Main(String[] args) in C:\Users\hansr\Documents\GitHub\CutilsFramework\CUtilsNET8\Main.cs:line 343
2024-09-12 03:12:23.977 Error Exiting - check log file
It does not see the
'data/diary.db' as a valid path for the diary (or it does not exist. Would it perhaps need '
./data/diary.db'?
If you say the diary.db is present in the data directory, I think you still have to look into the docker config for the mysql dll's (and maybe the
diary.db).
And btw: please could you switch Verbose off (set
TraceInfoLevel=info in the section
General). Verbose generates far too much information which is not required. It is only supposed to be used on my request

Re: docker cutils recent release not updating
Posted: Thu 12 Sep 2024 7:57 am
by Nossie
HansR wrote: ↑Thu 12 Sep 2024 5:57 am
And btw: please could you switch Verbose off (set
TraceInfoLevel=info in the section
General). Verbose generates far too much information which is not required. It is only supposed to be used on my request
done and yeah If never noticed that last one last night ... can I just confirm - are you aware of any other packages on here that are being used by cmx or cmx utils? thanks
Code: Select all
tzdata dotnet-runtime-8.0 unzip libudev-dev git python3-virtualenv gnupg2 lshw wget nano lsb-release
Re: docker cutils recent release not updating
Posted: Thu 12 Sep 2024 8:06 am
by HansR
CUtils only uses lshw, the other packages are irrelevant for running CUtils and afaics also irrelevant for running CMX.
Re: docker cutils recent release not updating
Posted: Thu 12 Sep 2024 8:16 am
by Nossie
some of them are QOL - but cutuils uses lsb-release as I found previously
I'll be honest Hans, I'm just not sure of this - yes I can share diary.db specifically, but the whole data folder is currently shared. If cutils is compiled not using the cmx sourcecode ...? and the diary is diary.db not diary.cs I just
I'll keep poking and thanks.
https://stackoverflow.com/questions/657 ... -not-found
In my meanderings last night I found references to nuget also - might add that back to the todo list
Code: Select all
root@67132ca8a623:/opt/CumulusMX# dotnet --info
Host:
Version: 8.0.7
Architecture: arm64
Commit: 2aade6beb0
RID: ubuntu.23.10-arm64
.NET SDKs installed:
No SDKs were found.
.NET runtimes installed:
Microsoft.NETCore.App 8.0.7 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]
Other architectures found:
None
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download
root@67132ca8a623:/opt/CumulusMX#
Re: docker cutils recent release not updating
Posted: Thu 12 Sep 2024 8:25 am
by HansR
There is no use of lsb-release in CUtils, I have no idea where that comes from.
CUtils is standalone, CUtils is compiled without CMX source code. It only gets some data from CMX which it set then hardcoded in the resulting website pages. The diary is diary.db, diary.cs is a source code file of CUtils which name you only see to indicate where the error takes place as Mark explained in the other thread. You only need to focus on the diary.db.
You might try to share diary.db explicitly and see what that leads to.
Re: docker cutils recent release not updating
Posted: Thu 12 Sep 2024 9:03 am
by Nossie
Code: Select all
MXWeather:
container_name: MXWeather
image: nossieuk/mxweather:dotnet-arm64
restart: unless-stopped
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
volumes:
- /media/DATA/WeatherServer/MXWeather/data:/opt/CumulusMX/data
- /media/DATA/WeatherServer/MXWeather/data/diary.db:/opt/CumulusMX/data/diary.db
- /media/DATA/WeatherServer/MXWeather/backup:/opt/CumulusMX/backup
- /media/DATA/WeatherServer/MXWeather/log:/var/log/nginx
- /media/DATA/WeatherServer/MXWeather/MXdiags:/opt/CumulusMX/MXdiags
- /media/DATA/WeatherServer/MXWeather/config:/opt/CumulusMX/config
- /media/DATA/WeatherServer/MXWeather/public_html/Reports:/opt/CumulusMX/public_html/Reports
- /media/DATA/WeatherServer/MXWeather/publicweb:/opt/CumulusMX/publicweb
- /media/DATA/WeatherServer/MXWeather/public_html:/opt/CumulusMX/public_html
- /media/DATA/WeatherServer/MXWeather/utils:/opt/CumulusMX/utils
- /media/DATA/WeatherServer/MXWeather/config/cumulusutils.ini:/opt/CumulusMX/cumulusutils.ini
- /media/DATA/WeatherServer/MXWeather/config/Cumulus.ini:/opt/CumulusMX/Cumulus.ini
- /media/DATA/WeatherServer/MXWeather/config/strings.ini:/opt/CumulusMX/strings.ini
- /media/DATA/WeatherServer/MXWeather/mqtt:/opt/CumulusMX/mqtt
- /media/DATA/WeatherServer/MXWeather/config/UniqueId.txt:/opt/CumulusMX/UniqueId.txt
- /media/DATA/WeatherServer/MXWeather/data:/opt/CumulusMX/datav3 # optional for migration
# - /media/DATA/WeatherServer/MXWeather/tmp/Easyweather.dat:/opt/CumulusMX/Easyweather.dat # Required to allow for n>
# - /media/DATA/WeatherServer/MXWeather/tmp/Easyweatherplus.dat:/opt/CumulusMX/Easyweatherplus.dat # Required to allow for n>
ports:
- 8998:8998
- 89:80
no difference :-/
I've tried chowning all the files to the correct user etc - I've tried mounting the file individually, I've tried removing the file completely - diary.db works fine locally
I might try changing back from ubuntu to Debian if dotnet is now native - it's not a huge issue but I'd rather not right now.
Re: docker cutils recent release not updating
Posted: Thu 12 Sep 2024 12:22 pm
by HansR
Ik have two remarks:
1) if you run website, there is no need to run sysinfo shortly thereafter. System info does not change within seconds.
2) In your list of files I do not see anything for SQLite. Do the libraries have no need for something special in docker?
Re: docker cutils recent release not updating
Posted: Fri 13 Sep 2024 7:25 am
by Nossie
ahhhh I didn't realise sysinfo ran as part of website - will sort that
So I added this to the packages installed and I've attached the log - the error has disappeared but the footer is still not updating
Code: Select all
# Install Packages
RUN apt-get update && \
apt-get install -y curl tzdata dotnet-runtime-8.0 unzip libudev-dev git python3-virtualenv gnupg2 lshw wget nano lsb-release sqlite3
Just noticed an error on the 2nd log so uploaded that.
Re: docker cutils recent release not updating
Posted: Fri 13 Sep 2024 3:36 pm
by Nossie
Hans, regarding the runtimes can you tell me more about those?
are they part of .net? do they have any special install on a linux distro? when I said about the lsb-release, is that being used to identify what architecture of the runtime to use? as I said that's a required package - or it throws up errors now atleast if you don't
Re: docker cutils recent release not updating
Posted: Sat 14 Sep 2024 7:21 am
by HansR
Hi Ian,
I will come back to your logs after the weekend.
Yes, the runtimes are part of .NET, they provide libs of packages for specific platforms. In this case only for SQLite. You probably only have to install the one for linux but I supply all generated by Visual Studio. You may experiment. You just need to copy the runtimes directory as a sub to the bin directory just as delivered in the distro.
I don't know about an lsb-release exec. It is not used by CUtils, afaik. I don't know where it - the error - comes from.
Re: docker cutils recent release not updating
Posted: Sat 14 Sep 2024 10:34 am
by Nossie
just to confirm this is the bin directory of utils?
Re: docker cutils recent release not updating
Posted: Mon 16 Sep 2024 7:32 am
by HansR
???
Re: docker cutils recent release not updating
Posted: Wed 18 Sep 2024 2:13 pm
by HansR
Hi Ian,
Do you have any progress?
I don't see any issue in your logs.