forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › Sja Crashes…
- This topic is empty.
-
AuthorPosts
-
-
June 3, 2007 at 4:13 pm #10358
DaleRG
Memberneed help….
have 5 dbases that all of a sudden just started not backing up….all of varying sizes….
would like to rectify this…..
what info/protocol is required….so that i can arrive at a solution….
error recieved is as follows, will happen now on all backup attempts and on varying stagers of the backup, different tables, etc….
the error seems to be that contact has been lost with SQLyogTunnel.php
have the dump files if they will help…
thanks in advance,
dale
-
June 3, 2007 at 8:39 pm #24069
peterlaursen
Participant“the error seems to be that contact has been lost with SQLyogTunnel.php”
This looks more like an issue with the server than with sQLyog/SJA. But a crash should not occur! Please tell the program version. If the program version is not recent please try a recent version and if porblem persists please attach dump files.
-
June 4, 2007 at 1:51 am #24070Member
updated to latest version and still crashing…..and using new SQLyogTunnel.php as well…..
i have the dmp and log files….
how do you wish to receive them?
it wont allow me to upload .dmp or .log files….
please advise….
Quote:HTTP Error. Could not connect to the tunneling URL.Job started at Fri Jun 01 11:30:00 2007Job started at Fri Jun 01 17:30:00 2007
Job started at Fri Jun 01 22:00:00 2007
Job started at Fri Jun 01 22:20:00 2007
Job started at Fri Jun 01 22:40:00 2007
Job started at Fri Jun 01 23:00:00 2007
HTTP Error. Could not connect to the tunneling URL.Job started at Fri Jun 01 23:30:00 2007
Job started at Sat Jun 02 11:30:00 2007
HTTP Error. Could not connect to the tunneling URL.Job started at Sat Jun 02 17:30:00 2007
Job started at Sat Jun 02 22:00:00 2007
Job started at Sat Jun 02 22:20:00 2007
Job started at Sat Jun 02 22:40:00 2007
HTTP Error. Could not connect to the tunneling URL.Job started at Sat Jun 02 23:00:00 2007
HTTP Error. Could not connect to the tunneling URL.Job started at Sat Jun 02 23:30:00 2007
Job started at Sun Jun 03 11:30:00 2007
Job started at Sun Jun 03 12:05:58 2007
Job started at Sun Jun 03 12:10:26 2007
Job started at Sun Jun 03 17:30:00 2007
Job started at Sun Jun 03 21:34:56 2007
HTTP Error. Could not connect to the tunneling URL.Job started at Sun Jun 03 21:38:24 2007
Job started at Sun Jun 03 21:41:36 2007
Job started at Sun Jun 03 21:44:35 2007
-
June 4, 2007 at 1:56 am #24071MemberQuote:Scheduled export started at: Sun Jun 03 21:34:56 2007
Exporting table ibf_admin_login_logs…Export successful…
Exporting table ibf_admin_logs…Export successful…
Exporting table ibf_admin_permission_keys…Export successful…
Exporting table ibf_admin_permission_rows…Export successful…
Exporting table ibf_admin_sessions…Export successful…
Exporting table ibf_announcements…Export successful…
Exporting table ibf_arcade_acthistory…Export successful…
Exporting table ibf_arcade_actihis…Export successful…
Exporting table ibf_arcade_activity…Export successful…
Exporting table ibf_arcade_cats…Export successful…
Exporting table ibf_arcade_challengeps…Export successful…
Exporting table ibf_arcade_challenges…Export successful…
Exporting table ibf_arcade_news…Export successful…
Exporting table ibf_arcade_scoreboard…Export successful…
Exporting table ibf_arcade_sessions…Export successful…
Exporting table ibf_arcade_tartemp…Export successful…
Exporting table ibf_article_cats…
Export job was unsucessful.
Error returned was: HTTP Error. Could not connect to the tunneling URL.
-
June 4, 2007 at 2:38 am #24072MemberQuote:SQLyog Job Agent Version 6.0
Copyright©Webyog Softworks Pvt. Ltd.. All Rights Reserved.
Job started at Sun Jun 03 22:31:08 2007Exporting table g2_AccessMap…Export successful…
Exporting table g2_AccessSubscriberMap…Export successful…
Exporting table g2_AlbumItem…Export successful…
Exporting table g2_AnimationItem…Export successful…
Exporting table g2_CacheMap…Export successful…
Exporting table g2_ChildEntity…Export successful…
Exporting table g2_Comment…Export successful…
Exporting table g2_CustomFieldMap…Export successful…
Exporting table g2_DataItem…Export successful…
Exporting table g2_Derivative…Export successful…
Exporting table g2_DerivativeImage…Export successful…
Exporting table g2_DerivativePrefsMap…Export successful…
Exporting table g2_DescendentCountsMap…Export successful…
Exporting table g2_Entity…Export successful…
Exporting table g2_ExifPropertiesMap…Export successful…
Exporting table g2_ExternalIdMap…Export successful…
Exporting table g2_FactoryMap…Export successful…
Exporting table g2_FailedLoginsMap…Export successful…
Exporting table g2_FileSystemEntity…Export successful…
Exporting table g2_G1MigrateMap…Export successful…
Exporting table g2_Getid3PropsMap…Export successful…
Exporting table g2_Group…Export successful…
Exporting table g2_ImageBlockCacheMap…HTTP Error. Could not connect to the tunneling URL.
Check C:Program FilesSQLyog Enterprisesja.log for complete error details.
HTTP Error. Could not connect to the tunneling URL.Total time taken – 100 sec(s)
-
June 4, 2007 at 2:41 am #24073MemberQuote:SQLyog Job Agent Version 6.0
Copyright©Webyog Softworks Pvt. Ltd.. All Rights Reserved.
Job started at Sun Jun 03 22:37:30 2007
Exporting table jos_acajoom_lists…Export successful…
Exporting table jos_acajoom_mailings…Export successful…
Exporting table jos_acajoom_queue…Export successful…
Exporting table jos_acajoom_stats_details…Export successful…
Exporting table jos_acajoom_stats_global…Export successful…
Exporting table jos_acajoom_subscribers…Export successful…
Exporting table jos_acajoom_xonfig…Export successful…
Exporting table jos_banner…Export successful…
Exporting table jos_bannerclient…Export successful…
Exporting table jos_bannerfinish…Export successful…
Exporting table jos_basic_db…Export successful…
Exporting table jos_blastchatc…Export successful…
Exporting table jos_blastchatc_users…Export successful…
Exporting table jos_booklibrary_lend_request…Export successful…
Exporting table jos_booklibrary_review…Export successful…
Exporting table jos_categories…Export successful…
Exporting table jos_components…Export successful…
Exporting table jos_comprofiler…Export successful…
Exporting table jos_comprofiler_field_values…Export successful…
Exporting table jos_comprofiler_fields…Export successful…
Exporting table jos_comprofiler_lists…Export successful…
Exporting table jos_comprofiler_members…Export successful…
Exporting table jos_comprofiler_plugin…Export successful…
Exporting table jos_comprofiler_tabs…Export successful…
Exporting table jos_comprofiler_userreports…Export successful…
Exporting table jos_comprofiler_views…Export successful…
Exporting table jos_contact_details…Export successful…
Exporting table jos_content…Export successful…
Exporting table jos_content_frontpage…Export successful…
Exporting table jos_content_rating…Export successful…
Exporting table jos_contxtd_details…Export successful…
Exporting table jos_core_acl_aro…Export successful…
Exporting table jos_core_acl_aro_groups…Export successful…
Exporting table jos_core_acl_aro_sections…Export successful…
Exporting table jos_core_acl_groups_aro_map…Export successful…
Exporting table jos_core_log_items…Export successful…
Exporting table jos_core_log_searches…Export successful…
Exporting table jos_docman…Export successful…
Exporting table jos_docman_groups…Export successful…
Exporting table jos_docman_history…Export successful…
Exporting table jos_docman_licenses…Export successful…
Exporting table jos_docman_log…Export successful…
Exporting table jos_easybook…Export successful…
Exporting table jos_easybook_code…Export successful…
Exporting table jos_facileforms_compmenus…Export successful…
Exporting table jos_facileforms_config…Export successful…
Exporting table jos_facileforms_elements…Export successful…
Exporting table jos_facileforms_forms…Export successful…
Exporting table jos_facileforms_packages…Export successful…
Exporting table jos_facileforms_pieces…Export successful…
Exporting table jos_facileforms_records…Export successful…
Exporting table jos_facileforms_scripts…Export successful…
Exporting table jos_facileforms_subrecords…Export successful…
Exporting table jos_gallery2…Export successful…
Exporting table jos_gallery2_useralbum…Export successful…
Exporting table jos_geo_visitors…Export successful…
Exporting table jos_geo_visitors_data…Export successful…
Exporting table jos_gmaps_category…Export successful…
Exporting table jos_gmaps_config…Export successful…
Exporting table jos_gmaps_icons…Export successful…
Exporting table jos_gmaps_maps…Export successful…
Exporting table jos_gmaps_markers…Export successful…
Exporting table jos_gmaps_points…Export successful…
Exporting table jos_groups…Export successful…
Exporting table jos_jcalpro_categories…Export successful…
Exporting table jos_jcalpro_config…Export successful…
Exporting table jos_jcalpro_events…Export successful…
Exporting table jos_jcalpro_themes…Export successful…
Exporting table jos_jcron_config…Export successful…
Exporting table jos_jcron_tasks…Export successful…
Exporting table jos_jl_app…Export successful…
Exporting table jos_jl_conf…Export successful…
Exporting table jos_jl_cron…Export successful…
Exporting table jos_jl_ip…Export successful…
Exporting table jos_jl_log…Export successful…
Exporting table jos_jl_log_entry…Export successful…
Exporting table jos_mambots…Export successful…
Exporting table jos_menu…Export successful…
Exporting table jos_messages…Export successful…
Exporting table jos_messages_cfg…Export successful…
Exporting table jos_modules…HTTP Error. Could not connect to the tunneling URL.
Check C:Program FilesSQLyog Enterprisesja.log for complete error details.
HTTP Error. Could not connect to the tunneling URL.
Total time taken – 222 sec(s)
-
June 4, 2007 at 5:07 am #24074
Rohit
Member1. Did you start facing this issue only after upgrading to SQLyog Enterprise 6? If not, which version of SQLyog Enterprise were you using before 6.0?
2. Are you using a shared hosting environment? Are you sure that the server is not restricting resources after serving a certain amount of load?
3. Lets start using the Ticket System at http://www.webyog.com/support. Pls. create a new ticket and attach the log and dump files after zipping them.
-
June 4, 2007 at 10:56 am #24075MemberRohit wrote on Jun 4 2007, 05:07 AM:1. Did you start facing this issue only after upgrading to SQLyog Enterprise 6? If not, which version of SQLyog Enterprise were you using before 6.0?
2. Are you using a shared hosting environment? Are you sure that the server is not restricting resources after serving a certain amount of load?
3. Lets start using the Ticket System at http://www.webyog.com/support. Pls. create a new ticket and attach the log and dump files after zipping them.
1. no, issue started using prior version…..prior version 5.29
2. yes, shared hosting using godaddy.com…..shared hosting plan, dedicated ip addy….not sure on the restriction…..but it happens on all dbase back up attempts….some dbases are 1 mg in size, the largest is 150 mg in size…..there are 5 in total each crash sja….but all backups worked flawlessly up until last weekend…..saturday……crashes happened frequently after that…..
3. will put in ticket as time permits…have to to work also….
-
June 4, 2007 at 11:31 am #24076Participant
we got your files and are analyzing!
but there is absolutely no change on the client side between when it worked ok and now?
-
November 18, 2008 at 9:09 pm #24077Member
back again… 😉
SQLyog607Ent
worked fine…..
got the notice that i needed an update and got the email…..
hummed and hawed…..finally broke down….
and updated to 713……and not same errors….
nothing changed…..worked flawlessly until this time…..
-
November 18, 2008 at 9:11 pm #24078Member
and/or what can be done to back up a 140 to 150 mg dbase and a number of smaller ones?
i have to do something to cyma…..
ideas?
-
November 18, 2008 at 10:32 pm #24079Participant
I do not understand what your are writing 10:09 PM . Did you have problems with previous versions that went away with 7.13 or opposite?
Please try to describe the problem you are facing now!
-
November 18, 2008 at 10:36 pm #24080Member
sorry peter, wrote that in a hurry…..
the previous versions worked fine…..
it is since upgrading that i am no longer able to back up my dbases…
forgive this old mans questions, but would there be other ways to back up the dbases other then a dump?
or can this be fixed or is there a work around to accomplish the same thing?
-
November 19, 2008 at 7:39 pm #24081Participant
1) First of all if you have problems with 7.13 and some older version works for you we will have to find such version for you until this has been solved (if you don't have the installer any more). What is the last version you tried and taht worked?
2) What iexactly s the failure here? Still the old issue 'cannot connect to tunneller'? Please describe as many details as you know!
3) Finally notice that sicne you upgraded an option was added for HTTP tunnelling. That is option to select a specific HTTP 'content type' for HTTP transfer. You find the option in the HTTP tab .. advanced. Please try all the options. You find some explanation in the help file.
-
November 19, 2008 at 7:57 pm #24082Member
yes still the same error…..cannot connect…
thank you peter, i will try your third option…..and let you know….
thanks again
-
-
AuthorPosts
- You must be logged in to reply to this topic.
