| Symptom: When launching Daylite Server Admin, you get an error code 300 with a domain name of com.marketcircle.MCPostgresDomain. This can happen after the Daylite server computer was shut down unexpectedly (power loss, force shut off, etc).
Potential causes:
-You could be running out of memory (hard drive space) on your computer. Please make sure you have at least 1GB of free space because we create a lot of short lived temporary files.
-An old server (postgres) process or a shared memory block is still running and preventing the personal storage environment from starting.
-You migrated your data from one computer to another and the storage environment is incompatible with the new computer. A typical scenario is migrating files from a PowerPC machine to an Intel machine.
Remedy
2) Restart the computer running Daylite Server Admin and try again.
Case 1:
If you see the following text patten then it means that a shared memory block is still in use or there is an old server (postgres) process running:
pg_ctl: another server might be running; trying to start server anyway
pg_ctl: could not start server
Examine the log output.
hared memory block (key 0, ID 65536) is still in use
2011-01-22 19:00:28.786 GMT [] - HINT: If you're sure there are no old server processes still running, remove the shared memory block with the command "ipcclean", "ipcrm", or just delete the file "postmaster.pid".
To resolve this issue perform the following steps:
1. Restart the computer and see if the shared memory block is released. If it is not, do the following in Terminal:
-Quit Daylite (if running).
-Launch Terminal from Applications > Utilities
- Copy and paste the following text in Terminal and hit [return] on the keyboard. After hitting [return], you will be prompted to enter your Mac OS X Password. While entering your password, please note that the cursor will not move. Once entered hit [return].
sudo ipcrm -m 65536
The ID number (65536 in this case) is important. It will be different for everyone.
Please make sure that no postgres process owned by _dayliteserver is running (check in Activity Monitor) when you execute this command. If the postgres process is running, the memory block will not be released.
- Quit Terminal.
2. Restart the computer.
3. Launch Daylite.
If you still receive the same error, repeat the steps above, but use the following terminal command instead:
sudo rm "/Library/Application Support/Daylite Server/Storage.dlsdb/Data/8_3/postmaster.pid"
Case 2:
If you see the following text pattern then it could be an issue where you transferred files from one machine to another (e.g. PowerPC to an Intel). If you see this error in the logs, please contact our support team for further assistance.
could not start server
GMT [] - FATAL: database files are incompatible with server
2011-02-15 19:24:59.537 GMT [] - DETAIL: The database cluster was initialized with PG_CONTROL_VERSION 1090715648 (0x41030000), but the server was compiled with PG_CONTROL_VERSION 833 (0x00000341).
2011-02-15 19:24:59.537 GMT [] - HINT: This could be a problem of mismatched byte ordering. It looks like you need to initdb.
Case 3:
Another possible cause for getting error code 300 is using other applications that run Postgres. In this case, specifically Lithium.
|
Symptoms:
- Every time you start Daylite Server Admin, it fails and displays error code 300.
- Uninstalling/Reinstalling has no effect.
-You'll notice something like this in your log files:
2010-09-25 20:06:21.116 EDT [] - DETAIL: Will not verify client certificates.
2010-09-25 20:06:21.129 EDT [] - FATAL: could not create semaphores: No space left on device
2010-09-25 20:06:21.129 EDT [] - DETAIL: Failed system call was semget(6116008, 17, 03600).
2010-09-25 20:06:21.129 EDT [] - HINT: This error does *not* mean that you have run out of disk space.
It occurs when either the system limit for the maximum number of semaphore sets (SEMMNI), or the system wide maximum number of semaphores (SEMMNS), would be exceeded. You need to raise the respective kernel parameter. Alternatively, reduce PostgreSQL's consumption of semaphores by reducing its max_connections parameter (currently 203). The PostgreSQL documentation contains more information about configuring your system for PostgreSQL.
Resolution:
Check the following forum post from Lithium's site:
http://support.lithium5.com/discussions/problems/254-postgres
|
|
