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.


Topics - eboxbuggy

Pages: [1]
1
edit: title might be confusing so here's a brief network description
192.168.0.1 ldap master
192.168.0.2 samba pdc
192.168.0.3 winxp client

Am trying to connect my WinXP SP3 workstation with the Samba PDC.

I've changed the domain name numerous times, gave every user admin access, rebooted, had coffee, drank water, had tea ... wth?

Am I missing something?  ???

/var/log/samba/workstation1
Code: [Select]
[2010/11/18 16:03:44,  0] lib/util_sock.c:539(read_fd_with_timeout)
[2010/11/18 16:03:44,  0] lib/util_sock.c:1491(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.

tail /var/log/messages
Code: [Select]
Nov 18 16:03:43 pdcserver smbd_audit: user1|192.168.1.x|connect|ok|IPC$
Nov 18 16:03:43 pdcserver smbd_audit: user1|192.168.1.x|disconnect|ok|IPC$
Nov 18 16:03:44 pdcserver smbd_audit: user2|192.168.1.x|connect|ok|IPC$
Nov 18 16:03:45 pdcserver smbd_audit: user2|192.168.1.x|disconnect|ok|IPC$

tail /var/log/syslog
Code: [Select]
Nov 18 16:08:33 pdcserver slapd[2591]: <= bdb_equality_candidates: (uid) not indexed
Nov 18 16:08:33 pdcserver slapd[2591]: <= bdb_equality_candidates: (memberUid) not indexed
Nov 18 16:08:33 pdcserver slapd[2591]: <= bdb_equality_candidates: (uid) not indexed
Nov 18 16:08:33 pdcserver slapd[2591]: <= bdb_equality_candidates: (memberUid) not indexed


2
Installation and Upgrades / Ebox just crashed
« on: April 17, 2010, 05:24:17 am »
My Ebox just crashed. I was adding new shares to samba and when I tried to logout it said something about a bug. I restarted the darn thing now it's FOOKED.

I tried to reconfigure everything again
Code: [Select]
/usr/share/ebox-usersandgroups/ebox-usersandgroups-reinstall
However it repeatedly gave me this error
Code: [Select]
Setting up ebox-office (1.4) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Processing triggers for ebox ...

(process:8882): GConf-WARNING **: Failed to stat /tmp/gconfd-ebox: Permission denied

(process:8882): GConf-WARNING **: Failed to stat /tmp/gconfd-ebox: Permission denied
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  2: IOR file '/tmp/gconfd-ebox/lock/ior' not opened successfully, no gconfd located: Permission denied) at /usr/share/perl5/EBox/GConfModule.pm line 48.
invoke-rc.d: initscript ebox, action "apache" failed.
Done.
Now you can go to 'Users and Groups -> Mode' and configure it again.

3
Installation and Upgrades / Samba just broke all of a sudden?
« on: March 26, 2010, 05:51:39 pm »
OMG guys. Here I go again. I'm not sure if my samba broke or is it my users & groups module.

Everything was working fine when users & groups was still at 1.4.2 updated both servers with the latest patches
Code: [Select]
sudo aptitude update && sudo aptitude safe-upgrade && sudo aptitude dist-upgrade
added a new user on my master ldap.
Code: [Select]
username: newuser group:allusers, accounting password:newuserI go into users & groups (newuser is a part of allusers & accounting group)

I now login to samba slave and check the users & groups. (newuser is NOT a part of any group)  ???

on a side note: adding new users takes like 2-3mins. is this normal?  ???

4
Installation and Upgrades / Is EBOX master fixed?
« on: March 12, 2010, 02:45:58 pm »
Hi it's been awhile since I visited the forums. Just a quick question. Have they fixed everything on master ldap + samba? Or do we still need to install samba on slave?

The reason I asked is because I find it useless to have my master on its own hardware without doing anything. Waste of resources to have that much hardware just serving LDAP. I was thinking of moving them to VM.

5
Nasty bug error was fixed by Isaac! Thanks dude! However you need to put in all your users/groups on master before enabling samba on your ldap slave.

All users and groups should be updated on the slave before enabling file sharing module ... well at least it works.  ;D

the link to the original report is here:
http://forum.ebox-platform.com/index.php?topic=2968.msg13320#msg13320


Pages: [1]