Midgard 1.6.3 – Datagard Errors – Resolved

As I discussed in my previous blog the problem I was having was with open files on OpenBSD with MySQL I thought at the time that adding the lines to the /etc/login.conf would resolve my problem. However I discovered that this did not resolve the problem. Why I don’t know unfortunately. The good news is the problem has been resolved. To resolve the errors of “Can’t create/write to file” and “Errcode: 9″ you have to start MySQL like so “mysqld_safe –open-files-limit=2048 &”. This will increase the amount of files MySQL can open therefore eliminating the errors. On a side note I did have to make some changes on permissions as shown below so Midgard could function which again were pointed out by Piotras. Thanks Piotras for the helping once again :-) . Your paths may vary as I installed Midgard CMS with a prefix path of /usr/local/midgard-1.6.3 to keep all the files centralized as possible.

# chmod -R 775 /usr/local/midgard-1.6.3/var/cache
# chown -R www:www /usr/local/midgard-1.6.3/var/cache
# chmod 551 /usr/local/midgard-1.6.3/var/lib/midgard/vhosts

If you care to read further on this subject of “mysql openfiles on openbsd” try the following links.

http://dev.mysql.com/doc/mysql/en/openbsd-2-8.html
http://www.monkey.org/openbsd/archive/misc/0502/msg01000.html

You can also use a search engine such as Google.com and search for with/out quotes “mysql openfiles openbsd”.

If Bill Gates were to build cars…

* Owner’s handbooks would have over 1300 pages and weigh over 3 pounds.
* Certain features would be unavailable on test drives (e.g. speeds exceeding 20Km/h, reverse gear, heater, etc).
* Guarantees would disclaim all promises that the cars were usable for travel.
* Opening the car door for the first time would signal acceptance of the guarantee terms.
* There would be a special “General car fault” indicator on the dash board.
* The car could only drive 5% of the roads, 10% of the time, without crashing.
* The steering wheel would have to be reinstalled every ten months.

How To Get A Life

It’s never easy to overcome innate nerdity, a serious Internet addiction, or a hard-core computer gaming habit, but trying usually isn’t as painful as kidney stones. Here’s how:

Let go of the mouse.

Turn off the computer.

Play a game of solitaire with a real deck of cards.

Eat something other than taco chips.

Fart without recording it and putting it up your Web page.

Get some sleep in bed rather than on your keyboard.

Next time you wake up in the middle of the night to go to the bathroom, don’t tell everyone on your ICQ list about it.

Open a window without turning your computer back on (yes, it is possible). Very gradually expose your eyes to increasingly bright light so as to avoid damage or permanent sun blindness.

When you feel prepared for a massive dose of non-CRT radiation, put on welding goggles and go outside.

If you see someone, say “Hi” to them instead of trying to make the modem connect sound.

Visit a friend that you haven’t spoken to in years because they don’t have an email address.

Have “.com” officially removed from behind your name. Go on a date with someone you didn’t meet in a chat room.

Bill Gates Meets His Match

The following is a conversation overheard as Bill Gates was moving into his new house…

Bill: “There are a few issues we need to discuss.”

Contractor: “Ah, you have our basic support option. Calls are free for the first 90 days and $75 a call thereafter. Okay?”

Bill: “Uh, yeah… the first issue is the living room. We think its a little smaller than we anticipated.”

Contractor: “Yeah. Some compromises were made to have it out by the release date.”

Bill: “We won’t be able to fit all our furniture in there.”

Contractor: “Well, you have two options. You can purchase a new, larger living room; or you can use a Stacker.”

Bill: “Stacker?”

Contractor: “Yeah, it allows you to fit twice as much furniture into the room. By stacking it, of course, you put the entertainment center on the couch… the chairs on the table… etc. You leave an empty spot, so when you want to use some furniture you can unstack what you need and then put it back when you’re done.”

Bill: “Uh… I dunno… issue two. The second issue is the light fixtures. The bulbs we brought with us from our old home won’t fit. The threads run the wrong way.”

Contractor: “Oh! That’s easy. Those bulbs aren’t plug and play. You’ll have to upgrade to the new bulbs.”

Bill: “And the electrical outlets? The holes are round, not rectangular. How do I fix that?”

Contractor: “Just uninstall and reinstall the electrical system.”

Bill: “You’re kidding!?”

Contractor: “Nope. Its the only way.”

Bill: ” Well… I have one last problem. Sometimes, when I have guests over, someone will flush the toilet and it won’t stop. The water pressure drops so low that the showers don’t work.”

Contractor: “That’s a resource leakage problem. One fixture is failing to terminate and is hogging the resources preventing access from other fixtures.”

Bill: “And how do I fix that?”

Contractor: “Well, after each flush, you all need to exit the house, turn off the water at the street, turn it back on, reenter the house and then you can get back to work.”

Bill: “That’s the last straw. What kind of product are you selling me?”

Contractor: “Hey, if you don’t like it nobody made you buy it.”

Bill: “And when will this be fixed?”

Contractor: “Oh, in your next house — which will be ready to release sometime near the end of next year. Actually it was due out this year, but we’ve had some delays…”

Midgard 1.6.3 – Datagard Errors – Continued

Piotras pointed out that the errors I was getting was due to open files issue with OpenBSD and MySQL. Piotras pointed me to an OpenBSD notes on mysql.com. I had no idea this error was pointing to an open files issue which apprently can affect all versions of OpenBSD. I read the notes and applied the changes to the /etc/login.conf file based on the comments submitted by name withheld. I added the following lines to my /etc/login.conf file.

Add the following 9 lines to your /etc/login.conf file
# Setting used by MySQL daemon
mysql:\
:datasize=infinity:\
:maxproc=infinity:\
:o penfiles-cur=2048:\
:o penfiles-max=8192:\
:stacksize-cur=8M:\
:localcipher=blowfish,8:\
:tc=default:

Now it looks like I’ve gotten most of the errors I received from datagard at instillation of the database. However I’m still getting one error as shown below. Any ideas on this one? I think if I fixed this last error things would be working again. If anyone knows what the error means and/or how to solve it let me know, thanks.

Datagard database installation error
Trying to create mysql database and blobs dir.
wait….

Updating database: multilang
repligard-Message: Reading config file /usr/local/midgard-1.6.3/etc/midgard/repligard.conf
repligard-Message: Importing /usr/local/midgard-1.6.3/share/midgard/languages.xml
repligard-Message: Reading config file /usr/local/midgard-1.6.3/etc/midgard/repligard.conf
repligard-Message: Making missing GUIDs…
repligard-Message: Reading config file /usr/local/midgard-1.6.3/etc/midgard/repligard.conf
repligard-Message: Making missing GUIDs…
Updating database: fixing cache
Updating database: version control
Updating database: quota support

Trying to create mysql database and blobs dir.
wait….

Trying to make xml update….

repligard-Message: Reading config file /usr/local/midgard-1.6.3/etc/midgard/repligard.conf
repligard-Message: Importing /usr/local/midgard-1.6.3/share/midgard/admin_user.xml

REPLIGARD/READ-CRITICAL **: Failed to allocate delayed resource f6b665f1984503790ed91f39b11b5392 as a link uid for member (Table ‘tmpxmlupdate.quota’ doesn’t exist).

Can not import admin user