Re: Ethernet connection weirdly not working mornings

2011-06-29 Thread Enno Gröper
Hello,

Am 29.06.2011 07:03, schrieb John Magolske:
 Since switching to a new machine and upgrading to the latest Sid, I've
 been having some weird problems getting a wired connection to the net.
 
 Running `ifup eth0` brings up a net connection -- but not in the
 morning for some reasontimes out with a No DHCPOFFERS received
 message. Repeatedly. I've been trying this every day for over a week,
 and like clockwork, morning = no connection, evening = connection.
 
 BUT, even though the ethernet connection doesn't work in the mornings,
 `ifup wlan0` will bring up a wireless connection in the morning just
 fine. This I'm not a morning-type ethernet is coming out of the very
 same NETGEAR wifi router that successfully provides a wifi connection
 any time of day.
 
 And when I try my old laptop (running a not-as-up-to-date Sid), it
 works fine, gets that ethernet connection in the mornings every time.
To bring light into this issue you shut sniff your ethernet traffic,
when bringing your interface up.
This could be done using wireshark or tcpdump.

Issuing
tcpdump -i eth0 -s 0 -w outfile

before ifup eth0, should give some valuable information.
You can kill tcpdump (Ctrl+C) after the DHCP timeout.

If you can't interpret the resulting capture yourself, you could post it
here.
Then we should be able to see the communication between the dhcp server
und your box.
Of course looking into the server logfile would be a good alternative to
this, but I suppose, that this isn't possible (with a reasonable amount
of effort) for a dhcp server running on a wifi router box.

Another idea: Could there be some kind of child protection running on
the wifi router preventing the access at some time interval for
specified computers?

HTH,
Enno



signature.asc
Description: OpenPGP digital signature


Re: Your favorite bug tracking system

2011-04-11 Thread Enno Gröper
Hi,

Am 11.04.2011 09:55, schrieb Frank Van Damme:
 2011/4/7 Carlos Miranda Molina (Mstaaravin) mstaara...@gmail.com:

 http://www.redmine.org/

 Integrate issues, wiki, etc.
 
 Very practical piece of software indeed, I have also used Trac which
 has more or less the same basic set of features (integration
 bugtracking-wiki-project management etc) and I consider Trac to be the
 more user friendly option (it accepts email in, in the release I
 used it was a not-hard-to-add-on feature). Redmine allows a lot more
 flexibility in roles though, you can also run multiple projects in one
 instance which is not possibly in Trac (need to create differenc
 instances + you can't have the same level in integration, pe. type
 #441 in a wiki page to link to bug in an other project).
I'm not sure what you guys are talking about, when writing about email
in and email ingestion, but redmine support controlling it using
email (change issues, create issues). Perhaps it could be a problem,
that it doesn't allow this for unregistered users.

http://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails#How-it-works

My 2 Cent,
Enno

P.S.: If you like Redmine, you should try ChiliProject:
www.chiliproject.org, which is a community fork of redmine.
https://www.chiliproject.org/projects/chiliproject/wiki/Why_Fork



signature.asc
Description: OpenPGP digital signature


After upgrade to squeeze system doesn't boot, because of not finding one disk using dmraid

2011-03-23 Thread Enno Gröper
Hi,
I already filed a bug about that [1] and now I hope somebody here can
help me.

I have some servers, where I have to use the hardware raid controller
PDC20277 (Promise Fasttrak). Under lenny it works fine using dmraid, but
after the upgrade to squeeze (to be exact: after upgrading kernel and
udev as mentioned in the upgrade guide [2]) the system doesn't boot
anymore, because only one of the to identical ide disks gets configured
and therefore the raid array is degraded and the system won't boot using
the raid array.

The reason for this seem to be new libata, which got introduced in
2.6.30 (I read that on the internet during my research) or the new pdc
driver (pata_pdc2027x instead of pdc202xx_new). Or something else I
don't see.

Any ideas? The only idea I have so far is using an older kernel with
debian squeeze. But then I wouldn't get security updates for it.

I don't get why the system configures one of the two identical disks but
not the other. It seems to see both disks:

 scsi2 : pata_pdc2027x
 scsi3 : pata_pdc2027x
and then following a similar ata3 and ata4 line (ata2.jpg attached to
bug report)

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618798
[2]
http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#upgrading-udev

Thanks in advance
Enno



signature.asc
Description: OpenPGP digital signature