This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
Hrm, are you seeing what URL's in particular are failing?
The site "scripts.virtualmin.com" appears to be online, but anytime it hits that site, it does so trying to download a particular application.
So it's possible something about the particular URL it's building isn't working in this case... and it'd be great to know which wasn't working! If you aren't seeing the URL, we may need to get Jamie involved, he'll be able to help us figure this out :-)
This morning (GMT-2) time, I recieved a couple of errors in my email
Digged a bit and it looks like a page on the server : scripts.virtualmin.com wasn't there
So I posted the above and disabled the collectinfo cronjob for 24 hours,
upon receiving your mail I retried the collectinfo.pl and it seems to work now.
Were there some pages missing some 5 รก 6 hours ago wich are in place now?
Can't see the full url wich was send by my server
I looked at etc/webmin/virtual-server/collectinfo.pl wich
exec-/usr/libexec/webmin/virtual-server/collectinfo.pl
The last one require ./virtual-server-lib.pl around line 205-- it reads :
Unfortunately, I'm not sure of why they wouldn't have worked earlier, but work now. I was hoping that if you saw the specific URL that failed, we could dig into that -- but since it's working now, and I don't know of anyone else who ran into the same problem, it might be hard to track down.
My suggestion would be to let us know if it happens again -- in fact, I might even suggest opening up a support request next time, so that Jamie can look into it a bit.
Hrm, are you seeing what URL's in particular are failing?
The site "scripts.virtualmin.com" appears to be online, but anytime it hits that site, it does so trying to download a particular application.
So it's possible something about the particular URL it's building isn't working in this case... and it'd be great to know which wasn't working! If you aren't seeing the URL, we may need to get Jamie involved, he'll be able to help us figure this out :-)
-Eric
This morning (GMT-2) time, I recieved a couple of errors in my email
Digged a bit and it looks like a page on the server : scripts.virtualmin.com wasn't there
So I posted the above and disabled the collectinfo cronjob for 24 hours,
upon receiving your mail I retried the collectinfo.pl and it seems to work now.
Were there some pages missing some 5 รก 6 hours ago wich are in place now?
Can't see the full url wich was send by my server
I looked at etc/webmin/virtual-server/collectinfo.pl wich
exec-/usr/libexec/webmin/virtual-server/collectinfo.pl
The last one require ./virtual-server-lib.pl around line 205-- it reads :
$script_ratings_host = "software.virtualmin.com";
$script_ratings_port = 80;
$script_ratings_page = "/cgi-bin/sendratings.cgi";
$script_fetch_ratings_page = "/cgi-bin/getratings.cgi";
$script_download_host = "scripts.virtualmin.com";
$script_download_port = 80;
$script_download_dir = "/";
$script_warnings_file = "$module_config_directory/script-warnings-sent";
$osdn_website_host = "sourceforge.net";
$osdn_website_port = 80;
$script_latest_host = "latest-scripts.virtualmin.com";
$script_latest_port = 80;
$script_latest_dir = "/";
$script_latest_file = "scripts.txt";
$script_latest_key = "latest-scripts\@virtualmin.com";
$upgrade_virtualmin_host = "software.virtualmin.com";
$upgrade_virtualmin_port = 80;
$upgrade_virtualmin_testpage = "/licence-test.txt";
$upgrade_virtualmin_updates = "/wbm/updates.txt";
$connectivity_check_host = "software.virtualmin.com";
$connectivity_check_port = 80;
$connectivity_check_page = "/cgi-bin/connectivity.cgi";
I simply tried scripts.virtualmin.com ans saw a fresh installed apache on centos page wich made me think the site was down.
Hope this helps.
John
Unfortunately, I'm not sure of why they wouldn't have worked earlier, but work now. I was hoping that if you saw the specific URL that failed, we could dig into that -- but since it's working now, and I don't know of anyone else who ran into the same problem, it might be hard to track down.
My suggestion would be to let us know if it happens again -- in fact, I might even suggest opening up a support request next time, so that Jamie can look into it a bit.
Thanks!
-Eric
Will do!
John