The support log can be larger than what GitHub allows

[EricClaeys]

The support log created by the "Getting Support" WebUI page or via the "support.sh" command can be over the 25 MB limit GitHub allows on file uploads.

The Allsky log files (/var/log/allsky.log, /var/log/allsky.log.1, and /var/log/allskyperiodic.log) are what takes most of the space, so if the log file will be over 25 MB, first don't include allsky.log.1. If the log file is STILL too big, only include a couple thousand lines from the remaining log files.

[EricClaeys]

@spanzetta,
If you do a "git pull" you will get an updated "support.sh" script that should work with support logs that are too big. It skips some log if they make the file too large.
Please try creating and uploading a support log again.

[EricClaeys]

Did ./support.sh --debug produce any output? It may have been on one of the dialog boxes.

[spanzetta]

Yes of course.. there was a text based dialog box.. and I went trough..
Isn't that what you asked for?
Pls clarify

[spanzetta]

pls note that I cannot download the one created yesterday following the procedure (the support log created with the text based dialog box)
How can I fix that?

[EricClaeys]

The support logs are in ~/allsky/html/support/, so you can go there and remove the old ones.

@Alex-developer,
Would it be possible to have the error message include the reason? Or point to a log file that has the reason?

[spanzetta]

Thanks.. deleted manually..

[EricClaeys]

Please do the following:

cd ~/allsky
mv support.sh support.sh-OLD
# Copy the attached file here
chmod 755 support.sh
./support.sh --debug

Whenever you see a line that has DEBUG on it, copy the line or take a screenshot. Those lines will tell me if the changes I made for > 25 MB are working.

You can remove the support logs that are over 25 MB.

Thanks - Eric

support.sh

[EricClaeys]

Thanks for the info. Please run:

cd ~/allsky 
git pull
# it will probably download a bunch of files, including a newer "support.sh" file
./support.sh  --debug

Upload ~/allsky/config/logs/support.log

Thanks

[spanzetta]

Thanks for the info. Please run:

cd ~/allsky 
git pull
# it will probably download a bunch of files, including a newer "support.sh" file
./support.sh  --debug

Upload ~/allsky/config/logs/support.log

Thanks

done

1. the file name is not support.log but support.log}

2. this is the file content:
   Tue Apr 28 13:58:16 CEST 2026 * Starting support log.
   Tue Apr 28 13:58:18 CEST 2026 DEBUG: Expected size of zipped log file: 4 MB, limit: 20 MB.
   Tue Apr 28 13:58:22 CEST 2026 * Ending support log.

3. this is the support log created

Thanks

[EricClaeys]

Thanks.

1. I fixed the support log file name. The } shouldn't have been there. Thanks for pointing it out.
2. Very interesting that your zipped files are much larger than mine. That implies your log files aren't compressing as much as mine.

Would you please run the following? It will give me an idea of how much your log files are compressed:

zip /tmp/allsky.log.zip /var/log/allsky.log
zip /tmp/allsky.log.1.zip /var/log/allsky.log.1
ls -h -l /tmp/allsky*.zip /var/log/allsky.log*

[spanzetta]

Here we go

admin@allsky:~ $ zip /tmp/allsky.log.zip /var/log/allsky.log
adding: var/log/allsky.log
zip warning: file size changed while zipping /var/log/allsky.log
(deflated 93%)
admin@allsky:~ $ zip /tmp/allsky.log.1.zip /var/log/allsky.log.1
adding: var/log/allsky.log.1 (deflated 93%)
admin@allsky:~ $ ls -h -l /tmp/allsky*.zip /var/log/allsky.log*
-rw-r--r-- 1 admin admin 2.2M Apr 29 19:51 /tmp/allsky.log.1.zip
-rw-r--r-- 1 admin admin 1.3M Apr 29 19:50 /tmp/allsky.log.zip
-rw-rw-r-- 1 root admin 18M Apr 29 19:50 /var/log/allsky.log
-rw-rw-r-- 1 root admin 31M Apr 25 23:59 /var/log/allsky.log.1
-rw-rw-r-- 1 root admin 2.5M Apr 18 23:59 /var/log/allsky.log.2.gz
admin@allsky:~ $

[EricClaeys]

Very interesting. You're getting 93% deflation, which means it's compressing the log files by 93%. That's very similar to what I'm getting, and my support logs are under 25 MB.

Would you please run:

cd ~/allsky 
git pull
./support.sh  --debug
ls -l html/support

And let me know what's in ~/allsky/config/logs/support.log.
Thanks.

[spanzetta]

here we go..

now for the 1st time I see the debug info in the popup

and
admin@allsky:~/allsky $ ls -l html/support
total 28176
-rw-rw-r-- 1 admin admin 28848419 Apr 30 08:09 support-AS-type-none-20260430080951.zip

and
1 Thu Apr 30 08:09:42 CEST 2026 * Starting support log.
2 Thu Apr 30 08:09:51 CEST 2026 DEBUG: Expected size of zipped log file: 28 MB, limit: 20 MB.
3 Thu Apr 30 08:09:51 CEST 2026 DEBUG: Expected size of zipped log file is 28 MB.
4 Thu Apr 30 08:09:51 CEST 2026 DEBUG: This is bigger than the GitHub limit of 20 MB.
5 Thu Apr 30 08:09:51 CEST 2026 DEBUG: Not including /var/log/allsky.log.1 gives a new size of 13 MB.
6 Thu Apr 30 08:10:56 CEST 2026 * Ending support log.

[EricClaeys]

I am going to have to rethink the logic.
The estimated size was 13 MB after not including the prior log file, but the actual size was 28 MB.

[spanzetta]

Ok let me know how could I help..

[spanzetta]

I just created it with the GUI button.. and it was 24,4 Mb..

support-repo-type-none-20260501205000.zip

[EricClaeys]

@spanzetta,
I just uploaded a version of support.sh with a much improved algorithm for determining the final support log size.
Please run:

cd ~/allsky
rm config/logs/support.log*
git pull
./support.sh

than attach ~/allsky/config/logs/support.log.

The size of this log file in ~/allsky/html/support should be similar to the one you did via the WebUI.

Thanks - Eric

[spanzetta]

Re: support.log: I'm glad you knew what I meant and not what I said! Sometime in the next day or three I will have a newer support.sh I'd like you to test which should decrease to log file even more.

sure.. I am more then happy if I can in some way contribute (even if with very little things)

In the meantime would you please upload the latest support log?

I did it now - after the update - from the GUI (is that ok?) ..
support-repo-type-none-20260507161653.zip

Going forward, instead of doing a "git pull", please run cd ~/allsky; ./upgrade.sh and pick the "in place" option. It will do the git pull then the "recreate_files".

I did that way... and I confirm it fixed the problem (didn't do the allsky-config recreate_files)

[EricClaeys]

If you run "upgrade.sh" and select the "in place" method you don't need to do a "git pull" or "allsky-config recreate_files", since upgrade.sh does them both.

Please run ./upgrade.sh and select the "In Place" method, then show me what's in ~/allsky/config/logs/support.log

Thanks

[spanzetta]

I did that already yesterday.. do you want me to do it again?
Maybe this time you want to see the content of upgrade.log and not support.log.. isn't it?

Pls clarify

Thanks

[EricClaeys]

Yikes I did it again. upgrade.sh writes to ~/allsky/config/logs/upgrade.log. It looks like it worked, so please use upgrade.sh going forwared.

Would you please create another support log, that let me know what's in ~/allsky/config/logs/support.log ? The newest support.sh should produce a slightly smaller support log and do a better job of keeping it under 25 MB.

[spanzetta]

argghh.. after the latest update (using upgrade.sh) the capture doesn't work anymore!

I see this error

and it goes in loop... it restart Allsky and again and again

2026-05-09T08:11:19.813070+02:00 allsky allsky[2477]: === Starting daytime capture ===
2026-05-09T08:11:19.813091+02:00 allsky allsky[2477]: ==========
2026-05-09T08:11:19.813111+02:00 allsky allsky[2477]: STARTING EXPOSURE at: 2026-05-09 08:11:19   @ 10.00 ms (0.01 sec)
2026-05-09T08:11:19.842782+02:00 allsky allsky[2477]:  >>> capture_RPi: WARNING: Unable to take picture, return code=0x7f00, WEXITSTATUS=0x7f
2026-05-09T08:11:19.848712+02:00 allsky allsky[2477]: ********************
2026-05-09T08:11:19.848880+02:00 allsky allsky[2477]: timeout: failed to run command ‘--thumb’: No such file or directory
2026-05-09T08:11:19.879077+02:00 allsky allsky[2477]: ********************
2026-05-09T08:11:22.838769+02:00 allsky allsky[2477]:      ***** Stopping Allsky *****
2026-05-09T08:11:27.381056+02:00 allsky allsky[2477]: STARTING EXPOSURE at: 2026-05-09 08:11:27   @ 10.00 ms (0.01 sec)
2026-05-09T08:11:27.984521+02:00 allsky allsky[2679]:      ***** Starting Allsky *****
2026-05-09T08:11:30.741368+02:00 allsky allsky[2963]: *** capture_RPi: WARNING: Unknown argument: [-cmd].  Ignored.
2026-05-09T08:11:30.741932+02:00 allsky allsky[2963]: *** capture_RPi: WARNING: Unknown argument: [rpicam-still].  Ignored.
2026-05-09T08:11:30.741957+02:00 allsky allsky[2963]: **************************************************
2026-05-09T08:11:30.741979+02:00 allsky allsky[2963]: *** Allsky Camera Software Version v2025.xx.xx ***
2026-05-09T08:11:30.742000+02:00 allsky allsky[2963]: **************************************************

Pls help me to fix it because currently my AllSky is NOT RUNNING..
Thanks

[spanzetta]

here is upgrade.log output

Sat May  9 08:05:17 CEST 2026 * STARTING REINSTALLATION OF v2025.xx.xx.

Sat May  9 08:05:29 CEST 2026 * Stopping Allsky
Sat May  9 08:05:32 CEST 2026 * Getting new files from GitHub
Sat May  9 08:05:35 CEST 2026 * 17 file(s) were downloaded.
Sat May  9 08:05:35 CEST 2026 * Look in '/home/admin/allsky/config/logs/upgrade-                                                                      files-downloaded.log' to see the list.
Sat May  9 08:05:36 CEST 2026 * Allsky upgraded.  Go to the WebUI to restart All                                                                      sky.

Sat May  9 08:05:36 CEST 2026 * Recreated files:
* Updating variables.json file.
* Updating sudoers file.
* Updating options file.
* Updating config_repo files.
* Updating variables used by C programs and running 'make' if needed.
* Updating lighttpd config file and restarting the service.
* Updating list of RPi supported cameras.
* Creating /home/admin/allsky/config/RPi_cameraInfo.txt with 'rpicam-still' entr                                                                      ies.
* Copying some /home/admin/allsky/config_repo files to /home/admin/allsky/config                                                                      .
Sat May  9 08:05:36 CEST 2026 * ENDING UPGRADE.

but in support.log I see no new code lines for the latest one (cannot attach because it's.. again... over 25Mb!)

[spanzetta]

@EricClaeys could you pls help me to recover the functionality?
I now have AllSky completely not working
Thanks

[EricClaeys]

Sorry about that - I broke it last night.

Please post the contents of ~/allsky/config/logs/support.log, then run:

cd ~/allsky; ./upgrade.sh
and select the Replace All option.

[spanzetta]

Sorry about that - I broke it last night.

Please post the contents of ~/allsky/config/logs/support.log, then run:

as said there is nothing new in support.log.. when I create a new report with GUI (I did it now) there is nothing related to it in support.log
I suspect also this logging was brokend

cd ~/allsky; ./upgrade.sh and select the Replace All option.

Does it keep everything of my setup ? I don't want to loose anything.. pls
Sorry but I was always doing upgrade (with git pull before and now with the new method) but I never did a replace all so I don't know what will happen..

[spanzetta]

I did it ... and now that problem is fixed.. but there is a new one!

When I access to variables (Overlay editor) I get this error

DataTables warning: table id=var-wx3ruwh-allskyVariable-table - Requested unknown parameter 'group' for row 0, column 1. For more information about this error, please see https://datatables.net/tn/4

and no variables appears..

:-(

see support log (now it's below 25Mb)
Uploading support-repo-type-none-20260509213441.zip…

and this is the support.log

admin@allsky:~/allsky/config/logs $ cat support.log
Sat May  9 21:34:39 CEST 2026 * STARTING SUPPORT LOG.
Sat May  9 21:34:40 CEST 2026 * Zipped size of everything EXCEPT log files: 0 MB.
Sat May  9 21:34:40 CEST 2026 * WORST CASE support log size: 10 MB is UNDER limit of 25 MB.
Sat May  9 21:34:43 CEST 2026 * ENDING SUPPORT LOG.

[EricClaeys]

Would you please run: do another "In Place" upgrade.sh, then create another support log and let me know what's in

cd ~/allsky
./upgrade.sh      # pick "In Place"
> config/logs/support.log
./support.sh

and let me know what's in ~/allsky/config/logs/support.log ?
I fixed a bug in support.sh

Thanks

[spanzetta]

Would you please run: do another "In Place" upgrade.sh, then create another support log and let me know what's in

There are few problems...

cd ~/allsky
./upgrade.sh      # pick "In Place"
> config/logs/support.log

when doing this I get

admin@allsky:~/allsky $ > config/logs/support.log
-bash: config/logs/support.log: Permission denied

./support.sh

when running this I get the following in the popup (but the support log is created)

/home/admin/allsky/scripts/installUpgradeFunctions.sh: line 179: /home/admin/allsky/config/logs/support.log: Permission denied
/home/admin/allsky/scripts/installUpgradeFunctions.sh: line 179: /home/admin/allsky/config/logs/support.log: Permission denied
/home/admin/allsky/scripts/installUpgradeFunctions.sh: line 179: /home/admin/allsky/config/logs/support.log: Permission denied

and let me know what's in ~/allsky/config/logs/support.log ? I fixed a bug in support.sh

nothing is written here because of the above

here is the generated support file created (very small)
support-AS-type-none-20260510090207.zip

Thanks

Let's try again ... ;-)

[EricClaeys]

Hmmm. That's strange. I have no idea why there's a permissions problem, but I know what the problem is based on the support log.

Please run:

cd ~/allsky
sudo chown admin  config/logs/support.log
sudo chgrp admin  config/logs/support.log

[spanzetta]

OK.. before I had:

admin@allsky:~/allsky $ ls -ld config config/logs config/logs/support.log
drwxrwxr-x 6 admin    www-data 4096 May 10 09:10 config
drwxrwxr-x 3 admin    www-data 4096 May 10 09:00 config/logs
-rw-r--r-- 1 www-data www-data  280 May  9 21:34 config/logs/support.log

then I executed the 2 commands

sudo chown admin  config/logs/support.log
sudo chgrp admin  config/logs/support.log

and then again

> config/logs/support.log
./support.sh

and now it did work..

and this is the support.log content

admin@allsky:~/allsky/config/logs $ cat support.log
Sun May 10 20:35:30 CEST 2026 * STARTING SUPPORT LOG.
Sun May 10 20:35:36 CEST 2026 * TEMP_DIR_OVERLAY=/tmp/allsky_W1v//config/overlay, TEMP_MY_MODULES=/tmp/allsky_W1v//config/myFiles/modules
Sun May 10 20:35:37 CEST 2026 * Zipped size of everything EXCEPT log files: 2 MB.
Sun May 10 20:35:37 CEST 2026 * WORST CASE support log size: 3 MB is UNDER limit of 22 MB.
Sun May 10 20:35:41 CEST 2026 * ENDING SUPPORT LOG.

and the support file
support-AS-type-none-20260510203537.zip

Let me know if that's ok now

And pls let me know how to fix the overlay variable manager issue

DataTables warning: table id=var-wx3ruwh-allskyVariable-table - Requested unknown parameter 'group' for row 0, column 1.
For more information about this error, please see https://datatables.net/tn/4

Before the latest update there was not such problem

[EricClaeys]

@spanzetta,
The support log looks good. The latest support.sh script doesn't include some large things we don't need, so I expected the size of the zip file to go down.

Alex is dealing with the DataTables message - see below.

[EricClaeys]

@Alex-developer,
Any idea about this error?

DataTables warning: table id=var-wx3ruwh-allskyVariable-table - Requested unknown parameter 'group' for row 0, column 1.
For more information about this error, please see https://datatables.net/tn/4

[Alex-developer]

https://datatables.net/tn/4

Thats one of the most cryptic errors datatables can return and has a lot of meaning. Is thsi code I can run to debug it?

[EricClaeys]

@Alex-developer,
Who are you asking if you can run the code to debug?

[Alex-developer]

@Alex-developer, Who are you asking if you can run the code to debug?

you :-)

[EricClaeys]

@Alex-developer,
I have no idea if that's code you can run. I don't know anything about datatables.
Sorry

[Alex-developer]

@Alex-developer, I have no idea if that's code you can run. I don't know anything about datatables. Sorry

No I meant is the support code all in Git, i.e. can I run the same code that the user is

[Alex-developer]

@spanzetta Can you post a support log that was created after you got the datatables issue?

[spanzetta]

You already have it.. I posted it under the report error (didn't you see it?)

UPDATE: Sorry... I realized it wasn't uploaded properly..
I now upload it again..
support-repo-type-none-20260509213441.zip

Let me know how to fix this issue (it was generated by the latest update.. )