Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
1
Installation and Upgrades / Re: Lost Web Interface
« on: October 15, 2009, 12:46:17 am »
Solution: ( with HUGE help from user jjmontes from #ebox channel )
edit /etc/sudoers and add:
ebox ALL = NOPASSWD:ALL
#<ebox>
# DO NOT MODIFY ANYTHING BETWEEN THESE MARKS.
# EBOX WILL OVERWRITE IT.
#</ebox>
Basically the problem was that the last, or one of the last apt-get upgrades that I did ended up overwritting the file with one without that line on it.
edit /etc/sudoers and add:
ebox ALL = NOPASSWD:ALL
#<ebox>
# DO NOT MODIFY ANYTHING BETWEEN THESE MARKS.
# EBOX WILL OVERWRITE IT.
#</ebox>
Basically the problem was that the last, or one of the last apt-get upgrades that I did ended up overwritting the file with one without that line on it.
2
Installation and Upgrades / Re: Lost Web Interface
« on: October 15, 2009, 12:18:23 am »
the output of ebox.log :
2009/10/14 22:57:00 INFO> Service.pm:619 EBox::Module::Service::restartService - Restarting service for module: network
2009/10/14 23:24:01 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/wu7sMMZtbL.cmd 2> /var/lib/ebox/tmp/stderr died with signal 9 without coredump
2009/10/14 23:50:43 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/HVPwbPAgwm.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:51:18 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/zrrLFwH35b.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:51:27 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/rxZgOBSjVa.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:51:29 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/UROqfDo9Zr.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:54:57 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/CvH4p4_xif.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:54:57 INFO> Service.pm:619 EBox::Module::Service::restartService - Restarting service for module: network
2009/10/14 22:56:26 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/UKtIEKKSF6.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
Sorry, try again.
sudo:
Sorry, try again.
sudo:
Sorry, try again.
sudo: 3 incorrect password attempts
2009/10/14 22:57:00 INFO> Service.pm:619 EBox::Module::Service::restartService - Restarting service for module: network
2009/10/14 23:24:01 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/wu7sMMZtbL.cmd 2> /var/lib/ebox/tmp/stderr died with signal 9 without coredump
2009/10/14 23:50:43 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/HVPwbPAgwm.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:51:18 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/zrrLFwH35b.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:51:27 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/rxZgOBSjVa.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:51:29 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/UROqfDo9Zr.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:54:57 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/CvH4p4_xif.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
2009/10/14 23:54:57 INFO> Service.pm:619 EBox::Module::Service::restartService - Restarting service for module: network
2009/10/14 22:56:26 ERROR> Error.pm:182 Error::throw - /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/UKtIEKKSF6.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo:
Sorry, try again.
sudo:
Sorry, try again.
sudo:
Sorry, try again.
sudo: 3 incorrect password attempts
3
Installation and Upgrades / Re: Lost Web Interface
« on: October 15, 2009, 12:07:23 am »
versions :
libebox
Version: 1.2.2-0ubuntu1~ppa1~hardy1
ebox
Version: 1.2.9-0ubuntu1~ppa1~hardy1
if I try to do /etc/init.d/ebox start I get the following at the command prompt :
sudo:
and that's it...
libebox
Version: 1.2.2-0ubuntu1~ppa1~hardy1
ebox
Version: 1.2.9-0ubuntu1~ppa1~hardy1
if I try to do /etc/init.d/ebox start I get the following at the command prompt :
sudo:
and that's it...
4
Installation and Upgrades / Re: Lost Web Interface
« on: October 14, 2009, 10:50:23 pm »
tried booting with the default ebox kernel and instead of being stuch at loading the 801q module it is stuck at some vconfig command, obviously, because with the default kernel I have no support for my network cards...
5
Installation and Upgrades / Re: Lost Web Interface
« on: October 14, 2009, 10:25:44 pm »
guys, I am stuck at this. Can someone from development tell me what happened with the last update for my box to stop working ?
6
Installation and Upgrades / Re: Lost Web Interface
« on: October 13, 2009, 04:16:01 pm »
yes! I have updated using apt-get update, apt-get upgrade.
7
Installation and Upgrades / Re: Lost Web Interface
« on: October 13, 2009, 03:57:30 pm »
Hi Javi,
can you give me some help regarding my problem ?
can you give me some help regarding my problem ?
8
Installation and Upgrades / Re: Lost Web Interface
« on: October 11, 2009, 10:33:54 pm »
Happened exactly the same thing to me, and I did just that: replace the permissions on that file. But it didn't solve my problem.
if I make a "ps ax" I get this:
3061 ? S 0:00 sh -c /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/cEmepdbUuJ.cmd 2> /var/lib/ebox/tmp/stderr
3062 ? S 0:00 /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/cEmepdbUuJ.cmd
and:
cat /var/lib/ebox/tmp/cEmepdbUuJ.cmd
/sbin/modprobe 8021q
and if I run /sbin/modprobe 8021 I get:
FATAL: Module 8021q not found.
The only change I made to the ebox instalation is that I am running a custom kernel. 8021q module is built into the kernel.
Everything was working great before the apt-get update, upgrade I make last friday night.
How can I solve this without compiling stuff as modules ? ( if this is the problem, of course! )
if I make a "ps ax" I get this:
3061 ? S 0:00 sh -c /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/cEmepdbUuJ.cmd 2> /var/lib/ebox/tmp/stderr
3062 ? S 0:00 /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/cEmepdbUuJ.cmd
and:
cat /var/lib/ebox/tmp/cEmepdbUuJ.cmd
/sbin/modprobe 8021q
and if I run /sbin/modprobe 8021 I get:
FATAL: Module 8021q not found.
The only change I made to the ebox instalation is that I am running a custom kernel. 8021q module is built into the kernel.
Everything was working great before the apt-get update, upgrade I make last friday night.
How can I solve this without compiling stuff as modules ? ( if this is the problem, of course! )
9
Installation and Upgrades / Re: dns forwarder
« on: July 30, 2009, 01:34:29 pm »
Hi SixStone!
Thanks for the tip!
Thanks for the tip!
10
Installation and Upgrades / Re: bonding with ebox is broken
« on: July 29, 2009, 11:57:19 pm »
Ok, I see. Thanks Javi!
So, another question:
why it is not supported ? it seems so simple! just add ifenslave as a dependency to the network module, add a drop down box to pick the interfaces to bond and write the config file
Great work you guys have been doing. It's unbelivable all you have made since I last tried ebox ( 6 months ago! )
btw: thanks for the tip
So, another question:
why it is not supported ? it seems so simple! just add ifenslave as a dependency to the network module, add a drop down box to pick the interfaces to bond and write the config file
Great work you guys have been doing. It's unbelivable all you have made since I last tried ebox ( 6 months ago! )
btw: thanks for the tip
11
Installation and Upgrades / dns forwarder
« on: July 29, 2009, 07:38:54 pm »
I also created a ticket for this:
there is no place where to configure the dns forwarder. this is a critical step of bind configuration!!
there is no place where to configure the dns forwarder. this is a critical step of bind configuration!!
12
Installation and Upgrades / bonding with ebox is broken
« on: July 29, 2009, 07:37:48 pm »
I just created a ticket for this, but basically bonding does not work:
Bonding in ebox does not work for several reasons:
- when creating a bond interface it is not possible to select the lan interfaces that will be part of the bond
- when creating the bond the user should also be able to choose what kind of bond mode ( 1,2,3,4, etc ) he will want to use ( 4 is the most used nowadays )
- the ifenslave package is not included on the ebox install cd or is not a dependency of the network module
- the configuration file create when creating a bond interface is not correct.
the created /etc/network/interfaces looks like this:
auto lo bond0
iface lo inet loopback
iface bond0 inet static
address 192.168.88.1
netmask 255.255.255.0
broadcast 192.168.88.255
gateway 192.168.88.254
and it should look like this:
auto lo bond0
iface lo inet loopback
iface bond0 inet static
address 192.168.88.1
netmask 255.255.255.0
broadcast 192.168.88.255
gateway 192.168.88.254
slaves eth0 eth1
bond-mode 4
bond-miimon 100
Bonding in ebox does not work for several reasons:
- when creating a bond interface it is not possible to select the lan interfaces that will be part of the bond
- when creating the bond the user should also be able to choose what kind of bond mode ( 1,2,3,4, etc ) he will want to use ( 4 is the most used nowadays )
- the ifenslave package is not included on the ebox install cd or is not a dependency of the network module
- the configuration file create when creating a bond interface is not correct.
the created /etc/network/interfaces looks like this:
auto lo bond0
iface lo inet loopback
iface bond0 inet static
address 192.168.88.1
netmask 255.255.255.0
broadcast 192.168.88.255
gateway 192.168.88.254
and it should look like this:
auto lo bond0
iface lo inet loopback
iface bond0 inet static
address 192.168.88.1
netmask 255.255.255.0
broadcast 192.168.88.255
gateway 192.168.88.254
slaves eth0 eth1
bond-mode 4
bond-miimon 100
13
News and Announcements / Re: eBox 1.0rc2 ready for testing
« on: January 30, 2009, 03:21:24 pm »
Great!!!
I just love bleeding-edge technology!
thanks alot
I just love bleeding-edge technology!
thanks alot
14
Installation and Upgrades / Re: File transfer
« on: January 25, 2009, 10:05:53 pm »
you should not open the samba ports on the internet side!!!! this is very dangerous!!
Set up the VPN and use it. As soon as you have your VPN up and running you will have ip connectivity with the eBox server and will be able to open and use the shares.
Set up the VPN and use it. As soon as you have your VPN up and running you will have ip connectivity with the eBox server and will be able to open and use the shares.
15
Installation and Upgrades / Re: File transfer
« on: January 25, 2009, 09:03:21 pm »
What do you mean for users outside the local network ?
If you have ip connectivity to the server it doesn't matter if users are on another network or not, as long as they can reach the server. If the users don't have ip connectivity to the server ( they are on a network that is not routed to the server ), then, you have to provide that ip connectivity, and you do this with a VPN. And for that, you can use the VPN server of eBox.
If you have ip connectivity to the server it doesn't matter if users are on another network or not, as long as they can reach the server. If the users don't have ip connectivity to the server ( they are on a network that is not routed to the server ), then, you have to provide that ip connectivity, and you do this with a VPN. And for that, you can use the VPN server of eBox.
Pages: [1] 2