os-git-backup error with 26.1-r2_2

Started by meyergru, January 28, 2026, 01:22:54 PM

Previous topic - Next topic
I got a log entry about a failed Github configuration backup, but I first thought this was because of a false positive in one of my blocklists blocking github.com. Now I found that when I started the configuration backup manually, I see an error on the web page reading:

Fatal error: Uncaught ValueError: The arguments array must contain 2 items, 1 given in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php:55 Stack trace: #0 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php(55): vsprintf('(/usr/local/bin...', Array) #1 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php(109): OPNsense\Core\Shell::exec_safe(Array, Array) #2 /usr/local/opnsense/mvc/app/library/OPNsense/Backup/Git.php(182): OPNsense\Core\Shell::shell_safe(Array, 'master:main') #3 /usr/local/www/diag_backup.php(395): OPNsense\Backup\Git->backup() #4 {main} thrown in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php on line 55

The stack trace in the crash reporter was:

[28-Jan-2026 01:08:12 Europe/Berlin] PHP Fatal error:  Uncaught ValueError: The arguments array must contain 2 items, 1 given in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php:55
Stack trace:
#0 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php(55): vsprintf('(/usr/local/bin...', Array)
#1 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php(109): OPNsense\Core\Shell::exec_safe(Array, Array)
#2 /usr/local/opnsense/mvc/app/library/OPNsense/Backup/Git.php(182): OPNsense\Core\Shell::shell_safe(Array, 'master:main')
#3 /usr/local/opnsense/scripts/system/remote_backup.php(17): OPNsense\Backup\Git->backup()
#4 {main}
  thrown in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php on line 55
[28-Jan-2026 13:11:24 Europe/Berlin] PHP Fatal error:  Uncaught ValueError: The arguments array must contain 2 items, 1 given in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php:55
Stack trace:
#0 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php(55): vsprintf('(/usr/local/bin...', Array)
#1 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php(109): OPNsense\Core\Shell::exec_safe(Array, Array)
#2 /usr/local/opnsense/mvc/app/library/OPNsense/Backup/Git.php(182): OPNsense\Core\Shell::shell_safe(Array, 'master:main')
#3 /usr/local/www/diag_backup.php(395): OPNsense\Backup\Git->backup()
#4 {main}
  thrown in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php on line 55
[28-Jan-2026 13:19:45 Europe/Berlin] PHP Fatal error:  Uncaught ValueError: The arguments array must contain 2 items, 1 given in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php:55
Stack trace:
#0 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php(55): vsprintf('(/usr/local/bin...', Array)
#1 /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php(109): OPNsense\Core\Shell::exec_safe(Array, Array)
#2 /usr/local/opnsense/mvc/app/library/OPNsense/Backup/Git.php(182): OPNsense\Core\Shell::shell_safe(Array, 'master:main')
#3 /usr/local/www/diag_backup.php(395): OPNsense\Backup\Git->backup()
#4 {main}
  thrown in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Shell.php on line 55
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+


January 28, 2026, 02:11:35 PM #2 Last Edit: January 28, 2026, 05:20:58 PM by meyergru
Yes, that fixes it.

But it is not in 26.1 final, so for now you need:

opnsense-patch -c plugins 4212ffea8c2c
configctl webgui restart
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

There will probably be a .1 next week for OpenSSL...

Exact same issue observed here on 26.1-amd64
I'm using multiple additional config backup options including manually saving plus GDrive and SFTP so this is low priority for me personally but as this is directly config related and as 26.1 is a major release version I suggest the fix is bumped if it likely affects multiple end users. Many thanks for raising this, nice to know I'm not the only one affected!

It will be hotfixed in a few minutes :)