ID |
Date |
Author |
Type |
Category |
Subject |
4098
|
Wed Dec 29 18:53:11 2010 |
rana | Summary | elog | found hung - restarted |
This was the error today:
GET /40m/ HTTP/1.1
Host: nodus.ligo.caltech.edu:8080
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://www.ligo.caltech.edu/~ajw/40m_upgrade.html
Cookie: elmode=threaded; __utma=65601905.411937803.1291369887.1291369887.1291369887.1; __utmz=65601905.1291369887.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); SITESERVER=ID=4981c5fd42ae53c9c9e0980f2072be4f |
4102
|
Mon Jan 3 10:32:27 2011 |
kiwamu | Summary | elog | found hung - restarted |
Found exactly the same error messages at the end of the log file.
Quote: #4098 |
This was the error today:
GET /40m/ HTTP/1.1
Host: nodus.ligo.caltech.edu:8080
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://www.ligo.caltech.edu/~ajw/40m_upgrade.html
Cookie: elmode=threaded; __utma=65601905.411937803.1291369887.1291369887.1291369887.1; __utmz=65601905.1291369887.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); SITESERVER=ID=4981c5fd42ae53c9c9e0980f2072be4f
|
|
4111
|
Wed Jan 5 10:45:51 2011 |
Koji | Update | elog | restarted |
Google bot crashed the elog again. Then, I found that Google bot (and I) can crash elogd by trying to show the threaded view.
There looks similar issue reported to the elog forum, the author did not think this is a true bag.
Note: This happens only for the 40m elog. The other elogs (ATF/PSL/TCS/SUS/Cryo) are OK for the threaded view.
Quote: |
Did it again. It seemed that Google bot came to the elog and tried to obtain "http://nodus.ligo.caltech.edu:8080/robots.txt". That was the last of the log.
Bot came from the AJW's homepage. Also Google FeedFecther came to the elog.
|
|
4114
|
Wed Jan 5 21:19:29 2011 |
Zach | Update | elog | restarted |
Restarted the elog with the script |
4121
|
Thu Jan 6 10:47:11 2011 |
Koji | Update | elog | ELOG fixed (re: restarted) |
Fixed the 40m elog crashing with the threaded display.
This morning I found that Google bot crashed the elog again. I started the investigation and found the threaded mode is fine if we use the recent 10 entries.
I gradually copied the old entries to a temporary elog and found that a deleted elog entry on August 6 had a corrupted remnant in the elog file. This kept crashed the threaded mode.
Once this entry has been eliminated again, the threaded mode got functional.
I hope this eliminates those frequent elog crashing.
Quote: |
Google bot crashed the elog again. Then, I found that Google bot (and I) can crash elogd by trying to show the threaded view.
There looks similar issue reported to the elog forum, the author did not think this is a true bag.
Note: This happens only for the 40m elog. The other elogs (ATF/PSL/TCS/SUS/Cryo) are OK for the threaded view.
Quote: |
Did it again. It seemed that Google bot came to the elog and tried to obtain "http://nodus.ligo.caltech.edu:8080/robots.txt". That was the last of the log.
Bot came from the AJW's homepage. Also Google FeedFecther came to the elog.
|
|
|
4168
|
Wed Jan 19 10:31:24 2011 |
josephb | Update | elog | Elog restarted again |
Elog wasn't responding at around 10 am this morning. I killed the elogd process, then used the restart script. |
4332
|
Mon Feb 21 11:05:51 2011 |
Zach | Update | elog | restarted |
I restarted the elog using the script. |
4334
|
Mon Feb 21 23:00:06 2011 |
Zach | Summary | elog | restarted |
again |
4365
|
Tue Mar 1 08:42:18 2011 |
Aidan | Update | elog | Restarted the elog this morning |
The elog was dead this morning. I reanimated it. It is now undead. |
Attachment 1: Zombie.gif
|
|
4378
|
Fri Mar 4 13:25:04 2011 |
Zach | Update | elog | restarted |
with script |
4438
|
Thu Mar 24 13:56:05 2011 |
josephb | Update | elog | elog restarted at 1:55pm |
Restarted elog. |
4556
|
Fri Apr 22 02:10:53 2011 |
Zach | Update | elog | restarted |
Restarted the elog with the script. |
4571
|
Tue Apr 26 22:56:35 2011 |
Zach | Update | elog | restarted |
with script |
4575
|
Wed Apr 27 20:14:16 2011 |
Aidan | Summary | elog | Restarted with script ... |
|
4741
|
Wed May 18 18:33:46 2011 |
Aidan | Update | elog | restarted elog with script |
|
4744
|
Thu May 19 00:15:20 2011 |
Jenne | Update | elog | Restarted, Italian-style |
Aka, from a hotel in Pisa. |
4745
|
Thu May 19 00:22:21 2011 |
rana | Update | elog | Restarted, Italian-style |
Quote: |
Aka, from a hotel in Pisa.
|
Restarted Thu May 19 00:21:49 2011 to recover from Jenne's Italian terrorism. |
4978
|
Fri Jul 15 19:00:18 2011 |
dmass | Metaphysics | elog | Crashes |
Elog crashed a couple times, restarted it a couple times. |
4998
|
Wed Jul 20 11:13:59 2011 |
Larisa Thorne | Update | elog | I restarted the ELOG as it seemed to have crashed |
 |
5232
|
Sun Aug 14 19:06:50 2011 |
Jenne | Update | elog | elog dead. Brought back to life |
like the subject says... |
5348
|
Tue Sep 6 21:00:48 2011 |
Zach | Update | elog | elog restarted |
I restarted the elog with the script as it was not up when I tried to make a post. It was again unresponsive when I went to submit, but this time the script couldn't restart it. The log said it couldn't bind to 8080, which usually happens if the daemon is still running. I pkilled it, then reran the script, and it appears to be working. |
5362
|
Wed Sep 7 20:44:11 2011 |
Suresh | Update | elog | restarted |
Elog crashed / dormant for long time. A look at the log file indicated that it was busy generating png thumbnails for pdf files.
Restarted at Wed Sep 7 20:41:13 PDT 2011
|
5556
|
Tue Sep 27 11:43:59 2011 |
Jenne | Update | elog | Elog has been dying a lot lately... |
WTF? |
5739
|
Tue Oct 25 21:23:17 2011 |
Dmass | Bureaucracy | elog | Elog Restarted |
Elog went nonreponsive. SSH'ed into nodus to run restart script. Elog came back ~15 minutes later. |
5750
|
Fri Oct 28 02:41:18 2011 |
Suresh | Metaphysics | elog | elog unresponsive: restarted |
Elog did not respond despite running the /cvs/cds/caltech/elog/start-elog.csh script two times.
It worked the after the third restart.
|
5785
|
Wed Nov 2 14:07:25 2011 |
Zach | Update | elog | restarted |
Elog was hanging, restarted with the script. |
5828
|
Mon Nov 7 11:50:42 2011 |
Jenne | Update | elog | Restarted elog |
Elog restart script killed the elog, but didn't restart it. Restarted by hand. |
5829
|
Mon Nov 7 12:51:44 2011 |
Zach | Update | elog | Restarted elog |
I've noticed that it always takes running the script twice for it to actually work. I think there's something wrong with how it's doing it. I'll mess with it sometime the elog isn't getting much use.
Quote: |
Elog restart script killed the elog, but didn't restart it. Restarted by hand.
|
|
5855
|
Wed Nov 9 19:08:18 2011 |
Suresh | Update | elog | restarted elog |
Elog was not responding and was restarted. |
5870
|
Fri Nov 11 00:58:19 2011 |
Den | Update | elog | restarted elog |
Elog suspended 2 times for 1 hour. Too high frequency.
Restarted. |
5902
|
Wed Nov 16 01:45:37 2011 |
Zach | Update | elog | restarted |
Elog was hanging. Restarted it with script. |
5903
|
Wed Nov 16 02:36:35 2011 |
Koji | Update | elog | restarted |
Basically, elog hangs up by the visit of googlebot.
Googlebot repeatedly tries to obtain all (!) of entries by specifying "page0" and "mode=full".
Elogd seems not to have the way to block an access from the specified IP.
We might be able to use http-proxy via apache. (c.f. http://midas.psi.ch/elog/adminguide.html#secure )
Or can we tweak the source of elod such that it does not accept "page0"?
GET /40m/page0?mode=full&new_entries=1 HTTP/1.1
Host: 131.215.115.52:8080
Connection: Keep-alive
Accept: */*
From: googlebot(at)googlebot.com
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Accept-Encoding: gzip,deflate
Quote: |
Elog was hanging. Restarted it with script.
|
|
5908
|
Wed Nov 16 10:13:13 2011 |
jamie | Update | elog | restarted |
Quote: |
Basically, elog hangs up by the visit of googlebot.
Googlebot repeatedly tries to obtain all (!) of entries by specifying "page0" and "mode=full".
Elogd seems not to have the way to block an access from the specified IP.
We might be able to use http-proxy via apache. (c.f. http://midas.psi.ch/elog/adminguide.html#secure )
|
There are much more simple ways to prevent page indexing by googlebot: http://www.google.com/support/webmasters/bin/answer.py?answer=156449
However, I really think that's a less-than-idea solution to get around the actual problem which is that the elog software is a total piece of crap. If google does not index the log then it won't appear in google search results.
But if there is one url that when requested causes the elog to crash then maybe it's a better solution to cut of just that url. |
5911
|
Wed Nov 16 12:21:33 2011 |
Koji | Update | elog | googlebot (Re: restarted) |
- elogd itself is a sort of web server which has no freedom to put our own file, we can not put robots.txt
- If we include elog using proxy in the usual web tree of Apache, we can put robots.txt at the root.
- So far, if we prevent "page0" browse by google, we will be saved for a while.
- It seems that the indexing is set to be refused by the following meta tags. But it does not prohibit googlebot to use "page0" URL, of course.
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"> |
5936
|
Fri Nov 18 00:25:10 2011 |
Zach | Update | elog | restarted |
with script. |
5977
|
Tue Nov 22 14:39:50 2011 |
Jenne | Update | elog | Afternoon elog restart |
Gave the elog its afternoon / tea-time reboot, since it was hanging yet again. |
5985
|
Wed Nov 23 00:30:55 2011 |
Zach | Update | elog | sucks |
Tried the script 3 times and it didn't come back. Pkill'd and then scripted. That worked. |
6001
|
Thu Nov 24 14:42:57 2011 |
Koji | Update | elog | elogd gained an immunity to googlebot |
I modified elogd.c as shown below in order not to allow to display all of the entries at once by specifying page number "0".
After this modification, elog seems to have survived 66 times of attacks by googlebots.
==============================
rossa:src>pwd
/cvs/cds/caltech/elog/elog-2.8.0/src
rossa:src>diff elogd.c_orig elogd.c
19912a19913,19917
>
> /* KA */
> if (page_n<1)
> page_n = 1;
>
|
6003
|
Thu Nov 24 15:48:27 2011 |
Illustrator | Update | elog | elogd gained an immunity to googlebot |


|
6443
|
Mon Mar 26 12:50:24 2012 |
Zach | Update | elog | restarted with script |
On the plus side, it was the first time I've had to do it in a while.. |
7136
|
Thu Aug 9 12:55:15 2012 |
Zach | Update | elog | elog was being a pain in the ass; I restarted it |
The elog was not responding. I attempted to restart it by running .../start-elog.csh, but this didn't work (even after the usual ~2 times it needs).
Somehow pkill did not kill the daemon, so I kill -9'd it and that did the trick. I ran the start script once more and it came back online. |
7351
|
Thu Sep 6 17:06:25 2012 |
Rijuparna Chakraborty | Configuration | elog | Cavitymode scan |
Aim: to scan the cavitymodes of IMC
The circuit used:
Attachment4
Results obtained:
Attachment 1,2,3
|
Attachment 1: 3.pdf
|
|
Attachment 2: 2.pdf
|
|
Attachment 3: 1.pdf
|
|
Attachment 4: cavityscanconnections.pdf
|
|
7435
|
Mon Sep 24 20:28:13 2012 |
rana | Summary | elog | restarted elog: was unresponsive |
|
8586
|
Wed May 15 23:38:04 2013 |
rana | Update | elog | categories trimmed |
I deleted a bunch of useless categories from the 40m elogd.cfg file. IF you find your category has been deleted, you can now learn how to categorize yourself into the existing categories. ELOG restarted and log file zeroed. |
9603
|
Wed Feb 5 18:36:56 2014 |
rana | Frogs | elog | MicroSoft BingBot is attacking us |
The ELOG was frozen, with this in the .log file:
GET /40m/?id=1279&select=1&rsort=Type HTTP/1.1
Cache-Control: no-cache
Connection: Keep-Alive
Pragma: no-cache
Accept: */*
Accept-Encoding: gzip, deflate
From: bingbot(at)microsoft.com
Host: nodus.ligo.caltech.edu
User-Agent: Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)
(hopefully there's a way to hide from the Bing Bot like we did from the Google bot)
|
10006
|
Fri Jun 6 14:56:09 2014 |
ericq | Update | elog | Aaaaaand we're back! |
ELOG is back up and running after last Friday's disk-crash-a-thon. SVN is still a work in progress. Jenne and I are now restarting computers and such. |
10096
|
Wed Jun 25 01:18:24 2014 |
Akhil | Update | elog | Weekly Update |
Plans for the Week:
- Phase and noise characterization of the UFC RF Frequency Counter.
- Characterization of the temperature actuator.
Progress and Problems Faced:
- Since past two days, I have been trying to measure the phase difference between the input and output signals of the FC using a 16 bit ADC ADS1115 (for input phase measurement) on Raspberry Pi(RPI).For that I have assembled a Circuit on a breadboard( Details will be mentioned in my next eLog).
- The interfacing and the codes seem to be alright but the RPI is not able to detect the address of the ADC chip. I will try to debug the issue as soon as possible and try to take data through the Pi so that I can have both delay and noise introduced by the FC.
- Now since the minimum sampling time of the FC has been brought down to 0.1s, I will test how accurately the FC is writing values every 0.1 s for a modulating input.
- The output data of the FC will be fitted into the input and the order of accuracy will be presented.Also the gain plots will be plotted at higher frequencies like 50 MHz, 100 MHz, 500 MHz and 1000 MHz using the network analyzer.
Work Inside the Lab:
- On Friday Morning I will go inside the lab with Manasa to make measurements from the NPRO to characterize its response to the temperature.
- I will be in the lab in the morning session(9 am- 1 pm) and make the required measurements. I will then analyze the data and by the end of the week will finish characterization of the FC and temperature actuator.
- For the rest of the time in this week, I'll be on my desk and will not be entering the lab.
Electronics Required:
- I will require the network analyzer on Wednesday and Thursday to make measurements at higher frequencies(30 MHz <F<1000 MHz) from the R PI.
Goal- By the end of the week:
- To characterize both the FC and the NPRO that would go into the FOL-PID loop.
- The FC will be ready to replace the network analyzers that are currently being used in the 40m.
|
10101
|
Wed Jun 25 14:52:22 2014 |
Andres Medina | Update | elog | Placing a lens between the steering mirrors and another lens between the second steering mirror and the cavity |
I was asked to calculate the lenses that we need in order to obtained a Gouy phase close to 90 degrees between the two mirrors that are in the Xend green. Yesterday, I measured the distances between the mirrors, and the distance between the mirror relative to the cavity as illustrate in the image attached below. I looked in to the 40m elog and Manasa did the last update on the length of the cavity. She measured 37.7 + 0.05m. The waist size of the beam that was measured by Annalisa in ID 8637 after the Faraday was w0=2.943e-5m @ -0.039m. I calculated the waist size inside the cavity, and I found a waist of w0=2.2 mm. My plan this week is to keep working in the calculation and finish all the calculation this week so that next week I can go inside and place the lenses. |
Attachment 1: SchematicForXendGreenGoingToTheCavity.pdf
|
|
10309
|
Thu Jul 31 18:54:03 2014 |
Chris | Frogs | elog | MicroSoft BingBot is attacking us |
Quote: |
The ELOG was frozen, with this in the .log file:
GET /40m/?id=1279&select=1&rsort=Type HTTP/1.1
Cache-Control: no-cache
Connection: Keep-Alive
Pragma: no-cache
Accept: */*
Accept-Encoding: gzip, deflate
From: bingbot(at)microsoft.com
Host: nodus.ligo.caltech.edu
User-Agent: Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)
(hopefully there's a way to hide from the Bing Bot like we did from the Google bot)
|
Yesterday elog was excruciatingly slow, and bingbot was the culprit. It was slurping down elog entries and attachments so fast that it brought nodus to its knees. So I created a robots.txt file disallowing all bots, and placed it in the elog's scripts directory (which gets served at the top level). Today the log feels a little snappier -- there's now much less bot traffic to compete with when using it.
We might be able to let selected bots back in with a crawl rate limit, if anyone misses searching the elog on bing. |
10311
|
Thu Jul 31 21:21:49 2014 |
Koji | Frogs | elog | MicroSoft BingBot is attacking us |
Oh, this is cool! Thanks!
I could not figure out how to place robot.txt as it was not so obvious how elogd handles the files in the "logfile" directory. |