This item is for system problems.  If something on Grex isn't working 
right (line noise on a modem, weird behavior from a program, etc.), 
this is the place to announce it.  Except for security holes.  If you 
find a hole in system security, mail information about it to "staff".

276 responses total.

did GreX have to be shut down just to roll the agora cf ?

This item should fill up real fast considering the ways things have 
been going here lately

I just read #2 and Grex froze and finally dropped out. I just got back on.
What was the cause and cure of this hiccup?

Via Backtalk, the current agora (autumn) jusst hangs when I try to do
anything.  All other confs work fine, as does accessing via telnet.

It was doing this before the Friday/Saturday downtime, if that matters.

Re #3:  It was one of our daily-or-so kernel panics.  :(   The system
rebooted itself automatically.

Re #4:  That's the "new agora" Backtalk glitch that's been around for a
while.  A workaround that usually works is to telnet or ssh to grex and
join agora via picospan (i.e. the "bbs" command) - after that, Backtalk
works with agora too.  (I'm entering this response via Backtalk, but did
join agora via bbs yesterday, which is why I don't think I got hit by
the glitch this time.)

Yep, working just dandy now. 

dandy pandy

re#7
The issue isn't confined to agora..of course.
backtalk crashes in coop all the time.

Hmm - not for me.  Are you getting actual crashing, or is it hanging?

re# 9
It  brings up about half the items...then it displays the "BACKTALK 
HAS CRASHED" error. It hasn't happened to me today.It happened 
constantly last week. I worked around the issue by telnetting in.

I haven't been able to connect to Backtalk for a week, either from home or
from work.  I just decided to try telnet and it worked, much to my
surprise.  Backtalk seems to time out over about 3 minutes.

I am now in via Backtalk.  Thanks to whoever got it working!  Once 
you're used to Backtalk, Picospan doesn't cut it any more.

unlucky !

Re #12:  I don't think anybody did anything to get Backtalk working.  It
seems to have a bug that causes it to hang, for certain users under
certain circumstances at certain times - and then suddenly start working
again for those users.  I don't think the cause has been fully diagnosed.

Backtalk stops working for me if I fiddle with any of its settings. When
it happens, I gotta blow away the config. This always fixes the problem.

I have had no problems at all with backtalk

Backtalk has several interfaces - pistachio, bubblegum, etc.  I use
pistachio and almost never have problems.  What interfaces are other
folks using?

vanilla.
it's problematic :(

I use pistachio.  I didn't do anything to fix Backtalk for myself, 
either.  It has resumed working for me both at work and at home, both 
at once.

It wasn't responding at all last week.  It looked to me like Grex was 
down.  I thought Grex *was* down.

Grex appears to have been down for almost 24 hours, though it did respond
to ping during at least some of that time.  The Grex Status page said it
was up, but it didn't respond to connections & last shows a crash/reboot.
There's nothing in the motd.

Er, that's not connected with jep's response.  This was yesterday afternoon
through this afternoon.

24 hours eh

hi tod !

"Yo Jim, those are some BAD threads!" -Pimp in Superman the Movie

This is the first time I've been able to log in since Sunday Oct 2.  
What's the story?

You get what you pay for

Then how do you explain m-net's uptime?

Pure spite?

Pure Sprite?

re #27
quantity vs. quality

On Saturday, Oct. 8, during the short interval between Grex outages, I 
discovered three rather large items in my email inbox (97K, 96K, and 97K). 
They were delivery failure notifications (DFNs) which seemed to indicate 
that mail, which I never sent, was sent with my return address in the 
headers. 

Those three items bounced, causing me to receive a DFN for each. If the 
original emails were spam, then the DFNs might have been the tip of the 
ice berg compared to the number of emails which may have actually been 
delivered to viable addresses. 

The following is the header of the first of the three DFNs:

    Date: Fri, 7 Oct 2005 09:51:04 +0530
    From: Mail Delivery System <postmaster@apnpdcl.co.in>
    To: rksjr@cyberspace.org
    Subject: Delivery failure notification

The following is supposedly the header of the original email which was 
included in the same (first) DFN:

    Date: Fri, 7 Oct 2005 10:00:25 +0530
    From: rksjr@cyberspace.org
    To: drbrain@ziemlich.org
    Subject: STATUS

I saved the full headers of all three DFNs.

I am wondering if anyone else might have received similar missives.

Re. #31: The first and third DFNs were from the same postmaster:

     From: Mail Delivery System <postmaster@apnpdcl.co.in>

     From: postmaster@manage.cyberoam

     From: Mail Delivery System <postmaster@apnpdcl.co.in>

The following line was from the full header of the second DFN:

     Received: from spooler by apnpdcl.co.in 

Thus indicating that all three DFNs were associated with the same 
"apnpdcl.co.in".

The three addressees of the original emails referred to in the DFNs were 
different:

     To: drbrain@ziemlich.org

     <munishwar.bajwa@pec.ac.in>:

     To: matt@oreilly.com

Has anyone else received similar notifications?

Hard to say.  There are a lot of viruses, etc, out there that generate mail
from more-or-less random addresses.  I think it likely that the rejection
notices you received are caused by such malware.

/dev/sd0j    13.5G  12.8G  -2.8M   100%    /log

Lots of annoying messages !

I've just removed some things from /log which bought back
a little space while I look further into it.

ThANKS

Filesystem  512-blocks     Used    Avail Capacity  Mounted on
/dev/sd0j     28261752 26944216   -95548   100%    /log

/log: write failed, file system is full

(Every response I read with fronttalk is giving me the write-failed message.)

Same with bbs.

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss