Closed (fixed)
Project:
vBulletin (and Photopost) to Drupal
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
26 Nov 2010 at 15:59 UTC
Updated:
1 Mar 2011 at 22:21 UTC
I keep getting the following error...
An HTTP error 502 occurred. /batch?id=12&op=do
any ideas?
Comments
Comment #1
liam mcdermott commentedIs this really on the -dev version? I'm just checking because it seems the stable version has a few problems that can be fixed by using the -dev version.
Thanks for reporting the bug and let me know for certain which version you're using. :)
(I really need to create a new stable release!)
Comment #2
mangus580 commentedYes i is. I had the original version in at first, found your mention of fixes in the dev, tried dev - still wont work. I even removed it totally and started over with the dev. no luck.
Comment #3
liam mcdermott commentedThanks very much for checking that. Unfortunately I have another question.
502 error is way too general for me to diagnose what's going on. Is there any more information with that error? Feel free to copy and paste it here.
Also, when you click the link to 'go back to the error page' (or whatever it is) are there any more error messages printed?
Comment #4
mangus580 commentedno other error.....
ran it again, only thing that changed was the ID is 14
Comment #5
liam mcdermott commentedUnfortunately just a 502 error is nowhere near specific enough for me to diagnose what's going on. :(
Older parts of the module still require the PHP timeout to be set, so it could be that your hosts don't allow scripts to increase it.
It could be that you're using Lighttpd or Nginx and the PHP daemon isn't responding within a particular time limit.
If you have access, the server logs might say more.
Sorry I can't help more than this. Please re-open this issue if you get more information though.
Comment #6
mangus580 commentedLiam - I am using a dedicated server that we own. What would you suggest I change with respect to the time limit for a new attempt?
Comment #7
mangus580 commentedLiam - what time out should i be looking at for this?? I would like to get this working so I can get on with my project.
Comment #8
liam mcdermott commentedMangus, sorry I meant to reply to this sooner, but other things cropped up and I forgot.
Did you find that the problem is definitely being caused by the PHP timeout?
I would suggest a timeout of ~2 hours. If it fails before 2 hours are up, then the problem is probably not due to the timeout. Reply here if that's the case and I'll try to think up some more stuff.
And if it works (let's hope so!) please pop back and mark the issue 'fixed'. :)
Comment #9
liam mcdermott commentedI should mention, the PHP timeout is in seconds, so: 2×60×60 = 7200.
You need a timeout of 7200.
Comment #10
mangus580 commentedThanks Liam, I will take a look this weekend.
Comment #11
mangus580 commentedNo love...
error:
An HTTP error 502 occurred. /batch?id=16&op=do
this was after maybe 5 minutes of the script trying to run
Comment #12
liam mcdermott commentedThe development version in CVS HEAD (the very bleeding edge, not available from the project page) has better reporting when/where it fails. Try following the instructions for checking out vB to Drupal from HEAD and try using that version of the module.
It should at least tell you where it's going wrong. Also, make sure you delete the existing vbtodrupal module directory before installing the one from HEAD. :)
If I cannot get more information on why/where it's going wrong, it's impossible to fix.
Comment #13
mangus580 commentedProgress!!
An error occurred while processing _vbtodrupal_convposts with arguments: Array ( [0] => [1] => 100000 [2] => vbtodrupal [3] => vbtodrupal )
Comment #14
mangus580 commentedUmmm newest version doesnt seem to have the delete_import url??
Comment #15
mangus580 commentedComment #16
liam mcdermott commentedSorry, it's been renamed to just
delete.Much better. It's not telling me precisely where or what is wrong, but I can make a pretty good guess based on this.
Am going to need to write some code to fix this, I'll try to fit it in this week sometime.
Comment #17
liam mcdermott commentedI've had a stab at fixing this. It's untested, so give it try (on a test site) and change the status back to active if it doesn't work.
If the importer gets further and fails on something different, please raise a new issue. Makes admin work and understanding issues easier. :)
Comment #18
liam mcdermott commentedOh, you'll need to get the latest version of HEAD from CVS, using
cvs up -dP.Just a FYI: I've also split a bunch of functionality out from the main vbtodrupal.module into individual module files and renamed them all to be more consistent.
Comment #19
mangus580 commentedGet the 502 still...
An HTTP error 502 occurred. /batch?id=24&op=do
When I return to the error page I get the following....
Comment #20
liam mcdermott commentedWhoops! Was just a stupid omission of a comma.
Try doing a
cvs up -dP, deleting, then running the import again.Comment #21
mangus580 commentedonward...
An HTTP error 502 occurred. /batch?id=27&op=do
Comment #22
mangus580 commentedComment #23
liam mcdermott commentedThat was a slightly subtler problem. I committed a fix and actually tested it this time, should be alright, for real!
This looks like a separate bug, am working on a fix right now...
Comment #24
liam mcdermott commentedRight, let's hope this is it. Update and try again, please! :)
Comment #25
mangus580 commentedAn HTTP error 502 occurred. /batch?id=30&op=do
Comment #26
liam mcdermott commentedAh, I already fixed this, update and try again.
I'm having trouble with the SQL query timing out now though, so you may want to wait until I've worked out a fix for that too. :/
Comment #27
mangus580 commentedlatest (although it looks the same as part of above?)
An HTTP error 502 occurred. /batch?id=31&op=do
An error occurred while processing _vbtodrupal_fixbbcode with arguments: Array ( [0] => [1] => 100000 [2] => vbtodrupal [3] => vbtodrupal )
Comment #28
liam mcdermott commentedThis looks like a separate issue, so I've put it in a separate bug report: #1062428: Error occurred while processing _vbtodrupal_fixbbcode()
Sorry for the bureaucracy. :)
Comment #29
mangus580 commentedHey - they all look the same to me!!