##### Last update 18 August 2020

# MBSE BBS Error Codes

This is a list of possible return codes from all MBSE programs and utilities. These codes can be used in scripts. If a program exits normally, the return code is 0. If a program exits by a signal, the return code is the signal number. This means if you kill a running program with a SIGTERM, the program exits with the SIGTERM error number, usually error number 15. These error codes are all nearly identical on all *nix platforms but there may be differences between distributions. Just do a `kill -l` to see a list of errors for your own platform.

Possible return codes:

100. Command line error
101. Configuration error
102. Initialization error
103. Full disk partition
104. UPS alarm detected
105. No valid recipients
106. Execute external program failed
107. Set TTY failed
108. File transfer error
109. File attach failed
110. Can't lock program, retry later
111. Node not in nodelist
112. Node may not be called
113. Can't make connection
114. Can't open TTY port
115. Node is locked
116. Node IP address not found
117. Unknown session type
118. Not Zone Mail Hour
119. Modem error
120. No modem port available
121. Session error (password)
122. EMSI session error
123. FTSC session error
124. WaZoo session error
125. YooHoo session error
126. Outbound scan error
127. Can't make poll
128. File request error
129. Error processing nodediff
130. Virus found
131. General error
132. Timeout error

The mailer can also return the following error codes:

201. TTY general error
202. TTY timeout
203. TTY EndOfFile
204. TTY Hangup
205. TTY Empty

When an external program is run, a MBSE program can exit with the return code of the external program with 256 added to it. So if the external program exits with error code 7, the code returned by the MBSE program is 263.

Go Back