I've been using Weblinks on one hosted site without a problem. Splendid module.

I installed it on another site I manage and each time I attempt to add a link, I kill the SQL server and make my service provider very unhappy.

I have uninstalled, deleted, DROPped, reinstalled, updated, and tried everything I can think of to get this to work. I can create link groups without error.

The catastrophic error occurs during the INSERT. After the server is restarted, the link that I tried to add, ends up as a node, promoted to the front page. The content type is Web link, but nothing appears in the Web Links overview page.

When I shut down the service, I need to contact my provider to start it up again. It makes troubleshooting this thing on my own rather cumbersome, so I was hoping someone might have a lifeline to toss out here.

Comments

rmiddle’s picture

rmiddle commented

What version of mysql are you running? That might help us with what is wrong.

Thanks
Robert

seanemmett’s picture

seanemmett commented

Thanks for the response. We're running mySQL 5.0.27.

I'm going to give it another try this week. This time around, I'll try adding the link first, before creating any groups, and see if that makes a difference.

rmiddle’s picture

rmiddle commented

seanemmett,

We get some reports with some of upgrades but no one else has reported an issues with a fresh install. I use that same version of mysql on my test server and never seen an issue.

Thanks
Robert

seanemmett’s picture

seanemmett commented

Thanks for the info.

This behavior (add a link and crash the server) has consistently occurred since I gave up on the links package and tried Web links. While I've upgraded twice since I first tried, that first attempt was after a fresh install.

It works just fine on one site (running Drupal, 6.4 on some flavor of Unix), but the problem is on another site (Drupal 6.6 on some flavor of Windows).

I'll remove all traces of the current install and see what happens when I start fresh. Ta.
-Sean

rmiddle’s picture

rmiddle commented
Status: Active » Postponed (maintainer needs more info)

Interesting. Do me a favor go in and change the Database type from Inno to MyISAM and see if that makes a diff?

Thanks
Robert

seanemmett’s picture

seanemmett commented

I've confirmed that the db type on the problematic install is Inno and I'm working with my admin to convert it to MyISAM. I'll let you know what happens. Thanks for the lead.

--
Seán

rmiddle’s picture

rmiddle commented

You only need to change the weblinks table. The rest should be fine. We are looking into it. But I suspect a glitch in MySQL inno implantation that we have found.

seanemmett’s picture

seanemmett commented

Well, thanks for guiding us through Scylla and Charybdis.

My sysadmin most graciously agreed to convert the weblinks table to MyISAM and that seemed to be the ticket. I can add a link without crashing his server.

I look forward to putting this great module to good use at long last. Thanks for all your help!

--
Seán

tallmark515’s picture

tallmark515 commented
Version: 6.x-1.2 » 5.x-2.2
tallmark515’s picture

tallmark515 commented

I had the same problem, changed the weblinks database type like you suggested and it works flawlessly. This is such a great module, perhaps you should consider posting this fix on the main page.

rmiddle’s picture

rmiddle commented
Version: 5.x-2.2 » master
Component: Performance » Code

tallmark515,

Was your database stored on mysql under windows? I suspect the issue is windows version specific and other modules have seen the same thing using inno under windows.

Thanks
Robert

tallmark515’s picture

tallmark515 commented

Yes the server is on Windows machine.

-mark

rmiddle’s picture

rmiddle commented
Status: Postponed (maintainer needs more info) » Fixed

I added the issue to our FAQ sections. Yea there is something with windows machines and inno database type. We need to setup a test enviorment to see if we can track down the query that is crashing mysql. But for now we have a work around.

Thanks
Robert

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.