Technology Errors

Redmine: Stuff To Do Plugin: Internal error: An error occured on the page you were trying to access

When installing the Redmine Stuff To Do plugin you might get the below error in your browser.

Error:
Internal error
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your redMine administrator for assistance.

Upon further investigation you will probably see another error similar to the below in the production.log under your Redmine installation.

Technology Errors

json/common.rb:122:in `parse’: 574: unexpected token at ” (JSON::ParserError)

I have been writing some scripts in ruby to parse JSON generated data. To do this it requires the json ruby gem which works great to parse through JSON output. Anyhow I was loading files into ruby and parsing them without issue until i got to a larger file and I received the below error.

Error:
/usr/local/lib/ruby/gems/1.8/gems/json-1.1.3/lib/json/common.rb:122:in `parse’: 574: unexpected token at ” (JSON::ParserError)
from /usr/local/lib/ruby/gems/1.8/gems/json-1.1.3/lib/json/common.rb:122:in `parse’
from tickets.rb:13
from tickets.rb:11:in `open’
from tickets.rb:11

Technology Errors

PostgreSQL SkyTools walmgr: CDTWARNING: archive_mode enabled, yet archive_command is not set

If you are running walmgr for log shipping with PostgreSQL and you see the below error in your postgresql.log file it is because you are missing the recovery.conf file. The recovery.conf file should be located in your data directory on the slave server which typically is /var/lib/pgsql/data.

Error:
CDTWARNING: archive_mode enabled, yet archive_command is not set

This means you probably have not run the below command as the postgres user on the slave server which is the command that actually generates the recovery.conf file.

Technology Errors

PostgreSQL SkyTools walmgr: Can’t boot Slave: DEBUG Only single loop requested, exiting

I ran into a silly error tonight during some configuration changes for PostgreSQL that took me awhile to figure out so I wanted to share so it might save others some time in the future. In an attempt to boot the slave server in a PostgreSQL SkyTools walmgr configuration I was unable to get it operational. The server would seem like it was stopping recovery mode however I was unable to login and the recovery process was still showing. Eventually I used the verbose switch to see if I could gain more information about why it was not booting up and the output is below.

Command:
walmgr.py conf/wal-slave.ini boot -v

Error:
2009-04-22 01:24:22,949 3899 INFO Stopping recovery mode
2009-04-22 01:24:22,949 3899 DEBUG Using pg_auth file from master.
2009-04-22 01:24:22,950 3899 DEBUG Execute cmd: ‘cp’ ‘/var/lib/pgsql/walshipping/logs.complete/pg_auth’ ‘/var/lib/pgsql/data/global/pg_auth’
2009-04-22 01:24:22,955 3899 DEBUG Only single loop requested, exiting