bordagen

In the office, we use a program called Daylite to manage our projects, contacts and jobs.

Yesterday, all heck broke lose and Daylite Server stopped working, claiming that the database could not be started and to try reinstalling or rebooting. So naturally being the expert with computers that I am, I turned it off and turned it back on again – still the same error (and yes, I also checked that it was plugged in).

After a little bit of solution hunting in the forums, trawling through posts of “Yes I have this problem !!!!111lol” and “Pls fix. kthnxbai” I managed to find a possible solution, rebuilt the system permissions. So I went ahead and did that and the error went away. Only it was replaced with a more worrying one – Database cannot be found! So a bit more hunting and I found another possible solution. This time to rebuild the permissions on the OpenBase database.

Tried that and then I get the original error back (for anyone searching, it was: com.marketcircle.MCPostgresDomain, Error 300). Now that I have come full circle, I try a different solution to the problem. This time from the official Market Circle Knowledge Base (which didn’t show up on my original search):

Go to /Library/Application Support/Daylite Server/Logs/Daylite Configd.log and check to see if see the following text pattern:

FATAL: pre-existing shared memory block (key 0, ID 65544) is still in use

If you see that text, then you can try to reboot the server to see if the shared memory block is released. If it is not, do the following in Terminal:

sudo ipcrm -m 65544

The ID number (65544 in this case) is important. It will be different for everyone.

Orignal post on the knowledge base can be found here

This seemed to work right away and now I can continue working through the To-Do list of jobs I have been given. Yay?

I finally managed to get a stable VNC connection to the office machines! Well, just the server at the moment, but that’s because it was the only machine on at the time…

I’ve been trying to get this sorted out since I was living at Liz’s parents house but there was a conflict with IP’s (the BT Home Hub and the work router had the same IP). There was a problem when we moved here too as the modem/router supplied to us by Be Internet was playing up not letting me change the IP address of it.

So yesterday I took a backup of the user settings, manually changed any reference to the existing IP to the new one and then ‘restored’ the settings from that edited file. Strangely it worked without a hitch!

The next step was getting a VPN connection working. This I already had set up – but it kept crashing out and being generally lagged on the old link, but with this new one (a different subnet) it not surprisingly worked.

From that internal connection I could SSH to the server, but not bring up a VNC window. I had to connect to the server from Liz’s Mac to change some settings (namely for the Remote Desktop to allow VNC conenctions with a password). Once this was sorted, I nabbed xtightvncviewer from the Ubuntu repositories via:

sudo apt-get install xtightvncviewer

And told it to connect. This worked very nicely, although it is quite slow but that is to do with the fact that I’m going over the Internet to make the connection rather than being in the same room as it.