Forum OpenACS Q&A: Backup script doesn't get sourced

However, the script doesn't seem to get sourced at server startup. There's no notice of it (nor any error related) in the server log and the backups don't get made.

I tested the script and it should be quite ok. I haven't changed any parts of the script related to scheduling the function so I guess they should be OK too.

Please see the script linked in the first message. I think it meets your requirements. There is, however, nothing related to scheduling nor making these backups in the log file. That is, I-search with "backup" in emacs doesn't give anything.

The script file has tcl extension. I have OpenACS 4.6, updated from cvs last time yesterday.

I renamed the file to backup-init.tcl but it didn't help, or at least there's no notice from this script when the server starts up. Here's a snippet from error log from the time of server restart. As far as I understand, server does sourcing directed in 0-acs-init.tcl and then jumps to load packages but does never source the backup file.

can't use non-numeric string as operand of "+"
    while executing
"expr { [lindex $a 5] + [lindex $a 2] }"
    (procedure "ad_scheduled_procs_compare" line 2)
    invoked from within
"ad_scheduled_procs_compare {t f {0 0} notification::sweep::sweep_notifications {-interval_id 4127 -batched_p 1} 1041855066 0 t} {f f 1800 rss_gen_serv..."
    (-compare command)
    invoked from within
"lsort -command ad_scheduled_procs_compare [nsv_get ad_procs .]"
    invoked from within
"foreach proc_info [lsort -command ad_scheduled_procs_compare [nsv_get ad_procs .]] {
    set bgcolor [lindex $bgcolors [expr { $counter % [llength $bg..."
    ("uplevel" body line 52)
    invoked from within
"uplevel {
      # /admin/monitoring/scheduled-procs.tcl

ad_page_contract {
    Displays a list of scheduled procedures.

    @author Jon Salz (jsalz..."
    (procedure "code::tcl::/web/suisse/packages/monitoring/www/scheduled-pro..." line 2)
    invoked from within
"code::tcl::$__adp_stub"
    invoked from within
"if { [file exists $__adp_stub.tcl] } {

      # ensure that data source preparation procedure exists and is up-to-date
      adp_init tcl $__adp_stub
..."
    ("uplevel" body line 3)
    invoked from within
"uplevel {

    if { [file exists $__adp_stub.tcl] } {

      # ensure that data source preparation procedure exists and is up-to-date
      adp_init t..."
    (procedure "adp_prepare" line 2)
    invoked from within
"adp_prepare "
    (procedure "template::adp_parse" line 30)
    invoked from within
"template::adp_parse [file root [ad_conn file]] {}"
    (procedure "adp_parse_ad_conn_file" line 7)
    invoked from within
"$handler"
    ("uplevel" body line 2)
    invoked from within
"uplevel $code"
    invoked from within
"ad_try {
$handler
      } ad_script_abort val {
# do nothing
      }"
    invoked from within
"rp_serve_concrete_file [ad_conn file]"
    (procedure "rp_serve_abstract_file" line 60)
    invoked from within
"rp_serve_abstract_file "$root/$path""
    ("uplevel" body line 2)
    invoked from within
"uplevel $code"
    invoked from within
"ad_try {
rp_serve_abstract_file "$root/$path"
set tcl_url2file([ad_conn url]) [ad_conn file]
set tcl_url2path_info([ad_conn url]) [ad_conn path_inf..."

True, it didn't have anything to do with the problem, but now I at least can check all the scheduled procs in a simple way.

I think the problem lies in this last scheduling part of the script:

if { ! [nsv_exists acs_pgbackup scheduled_p] } {                               
    ad_schedule_proc -schedule_proc ns_schedule_daily 0 0 acs_pgbackup
    nsv_set acs_pgbackup scheduled_p 1
    ns_log Notice "Backup has been scheduled."
} 

However, commenting out the if brackets didn't help the situation. I also changed the procedure definition of acs_pgbackup to ad_proc (instead of just proc), but it didn't help either.

As far as I know, the ad_schedule_proc row should be ok, and shouldn't that be the only thing that really matters?

If someone wants to check the latest version of the script as its whole, it would be totally magnificent.

The baseline still is, that not even the ns_log notice (on the last line of the script) nor any error message gets to the server log during the startup.

After that, my situation was just about the same than before the tricks, i.e. two different init files. The only difference was that I this time named the backup file acs-pgbackup-init.tcl. Now everything works just fine!

If what you mean is you couldn't find the nsv_* docs, that's a different story