this issue are very serious . We know that even before the problem occurred.
mr. The chuck similar problems submitted this announcement.
Do you have a plan other than Debian be produced by other distributions.
thank you read this. This problem was too bad, eh seriously these days.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I mentioned here: https://sourceforge.net/p/drbl/discussion/DRBL_live/thread/c416b76d/
Do you have 2nd DHCP server there?
You have to only keep one DHCP server, which is provided by DRBL live, in the same LAN. Otherwise the live-boot might lease the wrong IP address in the 2nd stage then fail to mount the NFS server.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
NO , i don't have 2nd DHCP server. The situation was even before the DHCP server.
single DHCP server is in this stualtion. what can i do???
plz answer. plz I have the install DRBL live in one environment. only same LAN environment. Do not misunderstand. thanks for reading
Last edit: an g w 2015-11-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can say 99.999% you have 2nd DHCP server in the same LAN, maybe you do not know that?
Try to use a closed network switch to test that and you can find it it will work.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Damian,
Your case is different from that of an g w. His case is actually denied by the NFS server, but yours is the client can not lease any IP address.
One of the possibilities is the newer Linux kernel does not support your network card very well. Try to check the log on your DHCP server, i.e. the /var/log/daemon, /var/log/syslog on DRBL server. To see if any request from your clients.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The error message on your attached photo is about available IP addresses number. Normally DRBL live starts with support for 100 clients. If you have booted more than 100 clients (or 50 clients with dual boots in the clients), then not enough IP addresses can be leased. Therefore you stop DHCP and start it again, the leases log will be cleaned. That's why it works there I believe.
BTW, one command you can use is:
sudo drbl-clean-dhcpd-leases
It should work for you in the same case.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
server side
As you can see, the server seems to be running normally.
client side part 1 (previous stuation to connected to server)
client side part 2(next stuation )
this issue are very serious . We know that even before the problem occurred.
mr. The chuck similar problems submitted this announcement.
Do you have a plan other than Debian be produced by other distributions.
thank you read this. This problem was too bad, eh seriously these days.
As I mentioned here:
https://sourceforge.net/p/drbl/discussion/DRBL_live/thread/c416b76d/
Do you have 2nd DHCP server there?
You have to only keep one DHCP server, which is provided by DRBL live, in the same LAN. Otherwise the live-boot might lease the wrong IP address in the 2nd stage then fail to mount the NFS server.
Steven.
NO , i don't have 2nd DHCP server. The situation was even before the DHCP server.
single DHCP server is in this stualtion. what can i do???
plz answer. plz I have the install DRBL live in one environment. only same LAN environment. Do not misunderstand. thanks for reading
Last edit: an g w 2015-11-02
I can say 99.999% you have 2nd DHCP server in the same LAN, maybe you do not know that?
Try to use a closed network switch to test that and you can find it it will work.
Steven.
Hello, i got same problem, and not always.
I'm using DRBL Live version, last testing version.
I got a closed network, only 2 computers(Server and one client for testing) connected to the switch.
And i can add some information, i got this problem sometimes, and i guess there is a problem with NIC drivers. I attach my screenshots. same problem.
If i use the stable version everything works fine, but got another problems that they are fixed in testing version.
@Damian,
Your case is different from that of an g w. His case is actually denied by the NFS server, but yours is the client can not lease any IP address.
One of the possibilities is the newer Linux kernel does not support your network card very well. Try to check the log on your DHCP server, i.e. the /var/log/daemon, /var/log/syslog on DRBL server. To see if any request from your clients.
Steven.
The NFS error cames after DHCP retrys, i'll check that logs thanks.
Is there any possibility to use another kernel or driver?
DHCP it's logging this, there is a DHCP configuration problem, because it's say's there is no IP for lease.
Last edit: Damián 2015-11-09
Hello again, i did more test, i got it working if i stop DRBL services, and start it again.
Example: Load LiveCD,
When S.O load's, Start DRBL, do things, STOP DRBL, run it again.
Now it works correctly.
The error message on your attached photo is about available IP addresses number. Normally DRBL live starts with support for 100 clients. If you have booted more than 100 clients (or 50 clients with dual boots in the clients), then not enough IP addresses can be leased. Therefore you stop DHCP and start it again, the leases log will be cleaned. That's why it works there I believe.
BTW, one command you can use is:
sudo drbl-clean-dhcpd-leases
It should work for you in the same case.
Steven.
Stop start? DRBL service?? huh.....-- then I didn't test . let's Test . i wish works correctly...
Thx.
@an g w,
Your case is different from Damián, I believe it's 2 DHCP server issue there. There is another thread about this:
https://sourceforge.net/p/drbl/discussion/DRBL_live/thread/c416b76d
Steven.