Mostly work related stuff which I would've entered into my "Log book". Instead of hosting it on an intranet site, outsourcing the hosting to blogger!
Monday, January 28, 2008
domains from godaddy
V has sent us a dozen domains like sai-inspires.org which he has purchased from godaddy. Logged on to godaddy, used the invite he gave, under domains -> AccountExec domains, hitting the + icon shows up our folder with the 12 domains. Did domain forwarding for all of them to http://media.radiosai.org/journals . Added the subdomain www for all of them too, forwarding to the same url. Also, for the forwarding to work, had to change the nameservers to "Default parked nameservers".
Sunday, January 27, 2008
lots of action, very few posts!
Once again a long backlog of stuff I should have posted long back:
- Recording morning and evening bhajans, so lots of time goes in recording and editing. Editing too, since otherwise hard disk would run out, and also PB want more bhajans asap for BhajanStream!
- heart2heart.in domain - purchased through rediff, a virtual server is made on fs1 for hosting this, and it's forwarded to http://media.radiosai.org/journals
- PB completed php-based scheduler internal web-app, beta-testing on.
- BV completed audio search page, open to public. This is really useful for me, when people ask for specific requests!
- Contemplating a sort of corporate blog or official blog - SP wanted to host a video on need for documentation, I read Eric Sink's book based on his blog, "The Business of Software", etc. Using blogger it should be straightforward, I hope...
- Stupid mistake of trying to make a minor change in number of pixels in TFD page, but without updating my local copy! Outage for 15 hours or so while I tried to replicate PB's changes... Funny part is that commenting out
if recordset.RecordCount > 0
makes the page work! - Following up on sssbpt.org migration to saiuniti servers - I'm not so good at HR! Too blunt!
- Installed Filezilla server, firewall yet to be opened.
- KR(M) is following up on the generator radiator issue, the generator batteries and the cooling tower fan-blades - as instructed by KVR.
- Doing saicast encodes on a borrowed HDD from PB, since my machine is FULL!
- Did some routine log analysis on fs1, transferring old log files to local for archiving.
Thursday, January 10, 2008
Virtualdubmod to directly convert mpeg2 to avi
In my earlier post, I'd described using autogk to convert mpeg2 to avi, then virtualdub to add the logo / watermark. Then an aha moment - autogk uses virtualdubmod, so why not use virtualdubmod directly do the watermarking etc? Used this method for Xmas 2007 videos.
Wednesday, January 09, 2008
BSNL name servers hate google
www.google.com has been unavailable from my location (AP) using BSNL's notorious name servers. So, using the post at Jason's blog, changed to the OpenDNS servers mentioned there, 208.67.222.222 and 208.67.220.220 - accessed it through gmail on krishna, vnc over ssh....
So now I can access blogger, youtube and gmail again!
Bonus - learnt about OpenDNS's adult filtering capabilities too.
So now I can access blogger, youtube and gmail again!
Bonus - learnt about OpenDNS's adult filtering capabilities too.
Friday, January 04, 2008
schedule page and mysql too many connections
Found this morning that mysql daemon had died on our hosting provider for radiosai.org , nettigritty. Contacted them, they said too many connections from radiosai user. They said
> 1. Do not use persisternt connections (pconnect)
> 2. Ensure you are correctly closing connections after use.
We're not using pconnect. For non-persistent connects, they are supposed to
automatically disconnect after the script executes, but still we have added
But two possible reasons could be
1. Too much traffic on our site
2. The times when our page fails to load properly giving the error
Maximum execution time of 30 seconds exceeded
( log file is at http://www.radiosai.org/program/inerror.log )
every time it fails, maybe the connection remains open.
Reason (1) - http://www.radiosai.org/plesk%2Dstat/webstat/ shows us that the
index.php gets 1000+ hits per day. That should be OK for mysql to handle, I suppose.
About Reason (2) - Another possibility I thought of was: the index.php also
has links to images and flash files, which also have to load before the 30
second timeout. If this can be delinked from the php part of the code - maybe
using div elements or something? - perhaps the timeout issue can be mitigated
to a large extent? For the time being, I've removed the links to the images and flash files and we'll see if this improves matters.
> 1. Do not use persisternt connections (pconnect)
> 2. Ensure you are correctly closing connections after use.
We're not using pconnect. For non-persistent connects, they are supposed to
automatically disconnect after the script executes, but still we have added
<?phpto the end of our scripts, just to be safe.
mysql_close($dbcon);
?>
But two possible reasons could be
1. Too much traffic on our site
2. The times when our page fails to load properly giving the error
Maximum execution time of 30 seconds exceeded
( log file is at http://www.radiosai.org/program/inerror.log )
every time it fails, maybe the connection remains open.
Reason (1) - http://www.radiosai.org/plesk%2Dstat/webstat/ shows us that the
index.php gets 1000+ hits per day. That should be OK for mysql to handle, I suppose.
About Reason (2) - Another possibility I thought of was: the index.php also
has links to images and flash files, which also have to load before the 30
second timeout. If this can be delinked from the php part of the code - maybe
using div elements or something? - perhaps the timeout issue can be mitigated
to a large extent? For the time being, I've removed the links to the images and flash files and we'll see if this improves matters.
a typical day
Once again I've to find more time in the allocated 24 hours - where is all the time going? Let's see. From Dec 16, this has been my schedule:
Before 8.15 am - finish morning routines including washing, cycling and exercise if any, and breakfast too.
8.15 to 10.15 - Morning bhajan recording at Mandir.
10.15 to 12.45 - Fight fires if any, or process the recorded audio
12.45 Lunch
1.45 to 2.30 - Make playlist or continue processing audio or if any videos ready for saicast, process them...
2.30 to 6.30 - Tea, then goto Mandir for programme or Bhajan recording
6.30 to 7.30 - Complete playlist making
7.30 Dinner
8.30 to 10.30 - @ S3, R&R, which quite often means updating the "voluntary" webpages!
The 2.30 to 6.30 slot is one where some optimization can be done. Maybe I can think of going to Mandir a little later, saving half an hour or so. Need to find time to do things like data backup, clearing up space on hard disks and so on.
Before 8.15 am - finish morning routines including washing, cycling and exercise if any, and breakfast too.
8.15 to 10.15 - Morning bhajan recording at Mandir.
10.15 to 12.45 - Fight fires if any, or process the recorded audio
12.45 Lunch
1.45 to 2.30 - Make playlist or continue processing audio or if any videos ready for saicast, process them...
2.30 to 6.30 - Tea, then goto Mandir for programme or Bhajan recording
6.30 to 7.30 - Complete playlist making
7.30 Dinner
8.30 to 10.30 - @ S3, R&R, which quite often means updating the "voluntary" webpages!
The 2.30 to 6.30 slot is one where some optimization can be done. Maybe I can think of going to Mandir a little later, saving half an hour or so. Need to find time to do things like data backup, clearing up space on hard disks and so on.
Subscribe to:
Posts (Atom)