Common problems and solutions
My log shows entries that say "monoLog is running in 30-day trial mode."
monoLog will run normally if you are using Rebound! or Kick-off!, or if you purchase an activator code. If the Rebound! or Kick-off! hardware is not connected to your computer, and you have not entered an activator code, monoLog will only run for thirty days. After this period, monoLog will no longer add any entries to its logs.
If you're using monoLog with Rebound! or Kick-off!, make sure your unit is properly connected to your computer, and there are no ADB or USB conflicts. See the Rebound! or Kick-off! user manual or online help for more troubleshooting information.
If you have an activator code, monoLog may not be able to find its preferences file. This can happen if you switch to a new version of Mac OS without copying your preferences. Select "Register..." from the Apple menu to re-enter your activator code.
Some items in my log don't appear in the order they actually occurred.
monoLog processes incoming log entries in the order they are received. Sometimes applications have delays in sending entries, or entries will be sent from several applications at once. These situations should be easy to spot, since their times will be almost identical.
A common situation that can occur is when an entry is sent while the system is still starting up. monoLog cannot receive these entries until it has finished initializing itself, so it may appear that entries are out of order.
For example, our Rebound! software sends a log entry after it restarts a crashed computer. This entry will be added to the log after monoLog has initialized. It will appear that Rebound! restarted the computer after monoLog started, but in reality, monoLog started after Rebound! restarted the computer.
I set up an E-mail Notifier, but I don't receive any mail when a log entry is received, even though I double-checked my e-mail address and SMTP server.
Some e-mail servers do not allow unknown users to send mail, in order to stop the possibility that an unauthorized person could use that server to send unwanted "spam", or junk e-mail.
To solve this problem, you can set up an account in your e-mail server whose username matches the name in monoLog's settings (which by default is "monoLog"). When your server receives mail from monoLog, it will then recognize the username and send the mail to its intended recipient.
I keep getting an error entry in my log which says "An error occurred opening the UDP socket listener." What does this message mean?
In addition to sending entries to logging programs on other computers, monoLog can receive entries from other computers (as well as some other network devices such as routers). To do this, monoLog sets up a "UDP socket listener" when it initializes at startup.
If another program is already using that port, monoLog will be unable to set up its listener, and you'll see this error message. You can disable this feature by unchecking the "Listen for network log data" box in the "General" preferences dialog box.
My computer always dials up my Internet Service Provider when monoLog starts up.
monoLog attempts to set up an Internet "listener" at startup (see previous question for more details). If your Remote Access (or in older systems, your PPP) control panel is set to "Connect automatically when starting TCP/IP applications," it will call your Internet provider when monoLog starts up.
To solve this problem, you can either disable this check box in your Remote Access or PPP control panel, or disable the network log listener as described above.