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.


Messages - Saturn2888

Pages: 1 [2] 3 4 ... 36
16
Both servers I administer which have both BackupPC 3.1.0 or 3.2.0 and Zentyal receive this error when connecting to the rsyncd share: "unexpected response rsync version 3.0.7 protocol version 30".  In more detail, ry doing rsync username@localhost:: I get:
Code: [Select]
rsync: server sent "rsync  version 3.0.7  protocol version 30" rather than greeting
rsync error: error starting client-server protocol (code 5) at main.c(1524) [Receiver=3.0.7]

I haven't touched these servers or changed a thing; the only difference is Zentyal upgraded from 2.0.1 to 2.0.x higher than that. I don't know exactly what version the error occurred, but I can tell you when the last daily backup occurred if that would help.

17
Installation and Upgrades / Cannot dist-upgrade four Zentyal packages
« on: October 29, 2010, 05:08:08 am »
What's going on with Aptitude, and how can I resolve these dependencies all dependent on each other? I went into Aptitude to try to fix it, but don't know how to select the "resolve" one. I'm assuming it's a simple matter of updating the entry in sources.list which shows "deb http://ppa.launchpad.net/zentyal/2.0/ubuntu lucid main"

Code: [Select]
root@ZENTYAL:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up ebox (2.0.6) ...
Error parsing XML:/var/lib/ebox/gconf.backupdpkg: error processing ebox (--configure):
 subprocess installed post-installation script returned error exit status 255
dpkg: dependency problems prevent configuration of ebox-network:
 ebox-network depends on ebox (>= 2.0); however:
  Package ebox is not configured yet.
 ebox-network depends on ebox (<< 2.0.100); however:
  Package ebox is not configured yet.
dpkg: error processing ebox-network (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ebox-usersandgroups:
 ebox-usersandgroups depends on ebox (>= 2.0); however:
  Package ebox is not configured yet.
 ebox-usersandgroups depends on ebox (<< 2.0.100); however:
  Package ebox is not configured yet.
dpkg: error processing ebox-usersandgroups (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ebox-samba:
 ebox-samba depends on ebox (>= 2.0.3); however:
  Package ebox is not configured yet.
 ebox-samba depends on ebox (<No apport report written because the error message indicates its a followup error from a previous failure.
                              No apport report written because the error message indicates its a followup error from a previous failure.
                              No apport report written because MaxReports is reached already
                                                                                            < 2.0.100); however:
  Package ebox is not configured yet.
 ebox-samba depends on ebox-network; however:
  Package ebox-network is not configured yet.
 ebox-samba depends on ebox-usersandgroups; however:
  Package ebox-usersandgroups is not configured yet.
dpkg: error processing ebox-samba (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 ebox
 ebox-network
 ebox-usersandgroups
 ebox-samba
E: Sub-process /usr/bin/dpkg returned an error code (1)

18
Installation and Upgrades / Re: Lost eBox access via https
« on: October 14, 2010, 09:28:08 am »
Apache2 is considered ebox webserver. ebox apache is the dashboard. It's a separate process.

19
Code: [Select]
root@main:~# ping vpn-client
PING vpn-client (2.2.1.6) 56(84) bytes of data.
64 bytes from 2.2.1.6: icmp_seq=1 ttl=128 time=63.5 ms
64 bytes from 2.2.1.6: icmp_seq=2 ttl=128 time=62.6 ms
64 bytes from 2.2.1.6: icmp_seq=3 ttl=128 time=61.0 ms
64 bytes from 2.2.1.6: icmp_seq=4 ttl=128 time=58.7 ms
64 bytes from 2.2.1.6: icmp_seq=5 ttl=128 time=69.9 ms
64 bytes from 2.2.1.6: icmp_seq=6 ttl=128 time=64.6 ms
^C
--- vpn-client ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 58.731/63.432/69.941/3.483 ms

As you can see, pinging the VPN clients from Zentyal works.


Code: [Select]
C:\Users\Kevin>ping vpn-client

Pinging vpn-client [2.2.1.6] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2.2.1.6:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

From a LAN-connected machine, I am unable to even though I'm receiving the right IP. I even tried creating a static route; it didn't work.

20
Installation and Upgrades / Re: Where do you run eBox on ?
« on: October 05, 2010, 08:46:52 pm »
What?

21
Nothing was wrong w/ my sources.list.
Code: [Select]
apt-get install iptables=1.4.4-2ubuntu2Fixed it.

22
Code: [Select]
ii  iptables             2:1.3.8.0debian1-1ub administration tools for packet filtering and NAT

23
I've been having this issue every since the upgrade from 1.5 to 2.0 on this machine and my subscription has been consistently pointing it out to me. I have no clue what this means or why it's happening, but is there a way to correct this issue?
Code: [Select]
2010/09/19 09:55:55 ERROR> Sudo.pm:212 EBox::Sudo::_rootError - root command /usr/share/ebox-network/ebox-flush-fwmarks
/sbin/ip route flush table 101
/sbin/ip rule add fwmark 1 table 101
/sbin/ip rule add from 1.1.1.1 table 101
/sbin/ip route add default via 1.1.1.1 table 101
/sbin/ip rule add table main
/sbin/iptables -t mangle -A PREROUTING  -m mark --mark 0/0xff -i eth0 -j MARK --set-mark 1
/sbin/iptables -t mangle -N EMARK
/sbin/iptables -t mangle -A PREROUTING -j EMARK
/sbin/iptables -t mangle -A OUTPUT -j EMARK
/sbin/iptables -t mangle -A EMARK -m mark --mark 0/0xff -j  MARK --set-mark 1 failed.
Error output: iptables: Protocol wrong type for socket
 iptables: Protocol wrong type for socket

Command output: .
Exit value: 1

24
Installation and Upgrades / Re: Samba module can't start
« on: September 19, 2010, 04:44:52 pm »
I fixed this problem by doing "rm /var/lib/ebox/tmp/samba.lock" then saving changes in Zentyal. It worked after that.

25
Installation and Upgrades / Re: Samba module can't start
« on: September 19, 2010, 04:40:48 pm »
I have this same problem no matter what I do on this specific machine. It just keeps saying "Could not get lock for service: samba" in the logs.

26
Oh ok, cool. I'll do that now. Thank you very much.

27
I can't have file sharing in use when a machine is setup as the LDAP Master correct? That's my problem. I want a machine with users that also acts as a file sharing server.

28
Isn't it possible to make an LDAP Master with no slaves and have that work with Zentyal? In 1.2 this was possible, but I've since forgotten how to do it in 1.3 and on. I just want to have users and enable file sharing and get rid of this whole user syncing.

29
I've tried making a static route and doing many other things, but I can't seem to ping any machines from inside the network that are connected via VPN. I have it so they can ping me and access everything, I've got it so my router, the Zentyal box, can reach those machines, but no matter what, I can't access those machines from anything inside of the network. Why is this? It used to work, but after upgrading, it no longer works. Does anyone have a solution?

30
:: Commands you need to get it working ::

cd /usr/share/ebox/www/js/scriptaculous/
wget http://script.aculo.us/dist/scriptaculous-js-1.8.3.tar.gz
gunzip scriptaculous-js-1.8.3.tar.gz
tar -xvf scriptaculous-js-1.8.3.tar
rm scriptaculous-js-1.8.3.tar
mv scriptaculous-js-1.8.3/src/* .
rm -r scriptaculous-js-1.8.3

Pages: 1 [2] 3 4 ... 36