was having a problem where startup did not complete and SSH never started, leaving me with only the console port.
by inserting a bunch of "write sys$output" statements in the systartup_vms.com file, I was able to track it down to starting the sys$print queue in error (it had been made into a generic queue with autostart).
The procedure aborted at this point with NO error messages or informational text.
Don't know where to put this, but startup should not fail silently....
I realize the fault was entirely mine for having a bad statement in the procedure.
Startup silently fails on queue errors
-
- Master
- Posts: 135
- Joined: Sat Aug 15, 2020 9:00 am
- Reputation: 0
- Location: Cambridge, UK
- Status: Offline
Re: Startup silently fails on queue errors
Errors in SYSTARTUP_VMS were always like this!
I recall a DEC engineer saying that you should reboot after ANY change in it - not easy on VAX that took 30 minutes (min) for a reboot, in a production environment...
You can set verify in startup, and log to a file
Chris
I recall a DEC engineer saying that you should reboot after ANY change in it - not easy on VAX that took 30 minutes (min) for a reboot, in a production environment...
You can set verify in startup, and log to a file
Chris
--
Chris
Chris
-
- VSI Expert
- Contributor
- Posts: 16
- Joined: Sat Sep 11, 2021 10:24 pm
- Reputation: 0
- Status: Offline
Re: Startup silently fails on queue errors
@tlovern
Do you have a reproducer?
Do you have a reproducer?
-
Topic author - Active Contributor
- Posts: 40
- Joined: Tue Jul 21, 2020 10:44 am
- Reputation: 0
- Status: Offline
Re: Startup silently fails on queue errors
I don't think I do at the moment, but I can probably re-create....
basically when I first brought up VMS I created a single print queue and used a raw telnet printer. This was my sys$print queue. This worked fine, and was basically a stop-gap until I could re-visit printing.
Went back to revisit printing:
I installed DCPS and created a LPD queue on my networked printer Then I modified sys$print to be generic with autostart on, with it pointing to my new queue.
I left the start/queue sys$print in my startup_vms file, and this is where it silently died.
like I said, entirely my fault. It would have been nice for the "start/queue" to complain loudly.
basically when I first brought up VMS I created a single print queue and used a raw telnet printer. This was my sys$print queue. This worked fine, and was basically a stop-gap until I could re-visit printing.
Went back to revisit printing:
I installed DCPS and created a LPD queue on my networked printer Then I modified sys$print to be generic with autostart on, with it pointing to my new queue.
I left the start/queue sys$print in my startup_vms file, and this is where it silently died.
like I said, entirely my fault. It would have been nice for the "start/queue" to complain loudly.
Last edited by tlovern on Tue Aug 22, 2023 6:55 pm, edited 1 time in total.
-
Topic author - Active Contributor
- Posts: 40
- Joined: Tue Jul 21, 2020 10:44 am
- Reputation: 0
- Status: Offline
Re: Startup silently fails on queue errors
so, my old-school solution was to simply put:
"write sys$output ===== entering <section name>"
and
"write sys$output ===== leaving <section name>"
wrappers around startup code I touch.
very old school, but effective - I know I'll fat finger something again.
"write sys$output ===== entering <section name>"
and
"write sys$output ===== leaving <section name>"
wrappers around startup code I touch.
very old school, but effective - I know I'll fat finger something again.