[Info-vax] Missing SMTP queue(s)

Steven Schweda sms.antinode at gmail.com
Sat Mar 19 16:10:03 EDT 2022


> the 'Generic server queue TCPIP$SMTP' is being defined and started by
> @SYS$STARTUP:TCPIP$SMTP_STARTUP 

   Ok.  Thanks.

> In a cluster with a common queue database, those generic
> TCPIP$SMTP_node_nn queues may be created for each node, depending on the
> setting of Number-Of-Queues-Per-Node : ... in
> TCPIP$SMTP_COMMON:TCPIP$SMTP.CONF

   Ah.  My cluster members have separate system disks, but there is a
common queue database (on ITS).  All I see in TCPIP$SMTP.CONF related to
queues is:
      Queue-Name                      : 
which looks pretty harmless.


   Further poking around found this in SYSTARTUP_VMS.COM (ahead of
TCPIP$STARTUP.COM):

[...]
$ THIS_NODE == F$EDIT( F$GETSYI( "SCSNODE"), "TRIM")
[...]
$! Keep SMTP mail delivery local.  Use the specific, local queue
$! (TCPIP$SMTP_node_1), not the generic, cluster-wide queue
$! (TCPIP$SMTP).
$!
$ if (this_node .nes. "")
$ then
$    define /system TCPIP$SMTP TCPIP$SMTP_'this_node'_1
$ endif
[...]

which changes the interpretation of the error message:
Starting execution queue TCPIP$SMTP got status %JBC-E-NOSUCHQUE, no such queue
%JBC-E-NOSUCHQUE, no such queue

   So:

ITS $ deassign /system TCPIP$SMTP

   After that, restarting the SMTP service seems to have gotten "Server
queue TCPIP$SMTP_ITS_1" recreated, which (along with a "tcpip analyze
mail /repair) seems to have restored normal e-mail operation.

   There's still no "Generic server queue TCPIP$SMTP_ITS_00", but ITS is
the only active cluster member at the moment.

   Node IT had been running V8.3-1H1, but i just updated it to V8.4-2L3,
so IT has been restarted repeatedly, which might explain some or all of
this.

   I'd guess that that definition of TCPIP$SMTP is less of a good idea
than it seemed to be years ago.  (Before "!SMTP rollover to ASCII
configuration in V5.7:"?  My SYSTARTUP_VMS.COM was dated 22-DEC-2017.)



More information about the Info-vax mailing list