Unofficial Roxen & ChiliMoon FAQs

If you have recently changed a nameserver setting for your domain it might fail to bind because its being cached by Roxen’s own DNS cache.

Flush the caches in the Tasks -> Maintenance tab.

Delete the files under roxen/var/demomodule-bookmarks/<your site>/.

Go to Tasks -> Maintenance -> Create site template

If you use relative paths in Roxen’s / ChiliMoon's configuration they always refer to the start directory (e.g. /usr/local/roxen/server/).

Don't worry if you find a regular error message “Update: Failed to connect to update server to fetch information about new packages” in event log. The update server has been out of work for a long time. It’s working again with Roxen 4.0 (well, at least it does not show any error messages, at the other hand i haven't recieved any update package so far).

You just have to move the current log, wait a couple of minutes, and then Roxen will start a new one at the old location on its own.

Additionally you may want to install a cron job to compress or remove old log files, e.g.:

 find /usr/local/roxen/logs/ -name 'Log.????-??-??' -mtime +7 \ 
     -exec gzip {} \; 
 find /usr/local/roxen/logs/ -name 'Log.????-??-??.gz' -mtime +30 \ 
     -exec rm {} \; 

This will gzip files after a week and remove them after a month.

• SIGHUP - Reloads the configuration
• SIGQUIT - Generate a thread dump
• SIGTERM - Restarts the server process
• SIGINT - Restarts the server process
• SIGALRM - Force ABS restart
• SIGKILL - Exit harder
• SIGABORT - Exit and generate a core dump

Run

	create_configinterface -a 

to create a new create a new administrator user with which you can change the password of the old one.

You can get more options of for creating a configuration interface (e.g. how to create with a batch process) by running

	create_configinterface --help 

You can get the address or port either by having a look at the configuration file for the administration interface (search for <var name='URLs'> by default in the file /configurations/Administration_Interface) or have a look into the debug log (logs/debug/default.1).

By default Roxen / ChiliMoon writes encoded user-agent identification strings (spaces are replaced by %20) to the log files. You have several solutions to solve this:

• Newer versions of Roxen allow to define the log string format with “$user_agent_raw” instead of “$user_agent”.
• Use Awstats log analyzer. It provides a configuration option to use it with Roxen’s / ChiliMoon's log files.

Error message: "Binding the port failed on <IP> for <url>."

If Roxen / ChiliMoon says it can&#8217;t register the port, it most likely failed to bind it. Reasons might be:

1. the server isn't running as root, which it may need to in order to bind low port numbers (below 1080),
2. some other process has already bound the port (check with lsof or some other similar program),
3. you've entered an explicit domain name, and DNS doesn't map this domain name to an IP address you can bind.

You can not run two https servers on the same IP and the same port. IP and port must together form an unique pair. If you have several virtual https servers, they need either different IPs or different port numbers. This is a restriction of the https protocol.

To turn off messages like this:

RXML parse error: Error in expr attribute: syntax error, unexpected '*' 
 | <set expr=" * 20" variable="var.thuows"> 
 | <cache minutes="30" variable="form.zopc"> 
 | <trimlines> 
 | <cache enable-protocol-cache="yes"> 

1. Go to the admin site (not /edit);

2. Find the module "Tags -> RXML parser" in the modules tree on the left;

3. Open the tab "RXML Errors";

4. Set "Quiet RXML parse errors" and "Quiet RXML run errors" to "Yes".

To force errors to be displayed regardless the configuration above, add <debug on> to the page code.