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] 5 6 ... 36
46
I wonder if you could run eBox on ARM with just that module in qemu since my main eBox machine doesn't have hardware VT. Maybe I could run it on another machine that does, but keeping Linux open on yet another server isn't the ideal.

I think your method of fixing it is the best overall because it's portable. Since there's no way to import/export your users, having a portable VM fixes that issue. I want to figure out how to do this myself now. The benefit is, you don't even need the LDAP server running; it only needs to be on when you are adding or removing users. I don't think it even needs to be on when you are changing passwords unless you have more than one slave machine.

In fact, now that you say that, the eBox devs could possibly build a VM module on top of the current eBox to handle this. It doesn't have to be a VM, but it could be something like how Virtual PC runs Windows XP applications in a VM Windows 7 or it could simply be installing two eBox applications, one of them specifically designed to handle LDAP serving. In fact, all of this could even be abstracted so the user never has to know that the machine is running both an LDAP master and slave in one box assuming that machine would be connecting to itself (which it would).

47
I thought the domain requirements would be a good thing. I mean, I thought it'd make things easier to fix up because all you have to do is point to the domain controller and it does the rest. For instance, I've yet to figure out how to connect Apache2, BackupPC, or any other Linux service to LDAP. Apparently 1.5 now includes a way to put LDAP users in PAM so that might make things less impossible for me when trying to authenticate using BackupPC, but it's still not that straight-forward. I think I'm just having problems with how confusing LDAP is and feel like there really should be an LDAP manager which configures these applications to work with LDAP for you. It's like typing "ldap-manager apache2 backuppc samba pam" and then it will configure those for you to use your LDAP users. I think it's very possible, but I don't know how much time or knowledge it would require to setup.

christian, have you seen my thread on getting Samba File Sharing working on the Master LDAP server? I've had it working for months so I really don't understand the restriction either.

48
1. Oops, I knew the answer to this one; didn't mean to ask it.

2. http://forum.ebox-platform.com/index.php?topic=4382.0 <- I am still able to get file sharing working on an LDAP Master. I tried it 8 times this morning, and it worked each time both 1.4.8 and 1.5.8. What would it do if you enabled both. I've asked before, but since it works for me, I can never get a straight answer from anyone. I am hoping an eBox dev will try testing my methodology and figure out why it works for me.

3. I was wanting to see if the Master could be an AD PDC only, not an LDAP server but be able to be connected to by eBox Slaves. Is there any method of joining eBoxes to a domain controller in the WUI? I was hoping something like that would be implemented and along with it, a way for the Master to be only an AD PDC and get rid of all that LDAP jargon. My intent was that this would allow File Sharing on the Master without having to assign it slaves.

49
I'm having this exact same problem using a 1.4.8 Slave to connect to a 1.5.8 Master. I wish I could fix it. It's strange when the Master thinks the Slave is there even when it couldn't connect.

50
eBox 1.4.8 & 1.5.8
2.6.24-28-server & 2.6.32-24-generic-pae

:: BACKGROUND ::

Many of you on the forums probably know I'm the only one who got File Sharing working on an LDAP Master. I'm here to give you that information now on how I actually did it. Right now, I have it working again, even on a different machine, and I am hopeful this will work for everyone else. I have confirmed this works in eBox 1.3, 1.4, and 1.5.

:: SOLUTION ::

The solution is extremely strange. It requires the right timing of when you do which commands, and I've sort of forgotten already how I did it, but here's what you can do to fix it all. Some of these steps are unneeded, but I don't know which so here's everything I can remember doing step-by-step. The very first thing to know, do not add users or configure Samba before you've typed in and synchronized the LDAP Slave with the Master.

NOTE: THIS WILL DELETE ALL YOUR CONFIGURED USERS, GROUPS, AND SHARES

1. /usr/share/ebox-usersandgroups/ebox-usersandgroups-reinstall
2. Go into the WUI and enable Users & Groups module in the Master
3. Connect the Slave(s) immediately
4. Enable the File Sharing module (it won't work properly)
5. Save WUI
6. /usr/share/ebox/ebox-unconfigure-module samba
7. Enable File Sharing module

... ~ !! Yay! It works !! ~ ...

:: NOTES ::

Don't forget to re-enable ldap for Internal Networks to eBox in the Firewall Rules.

51
:: SOLUTION ::
Download http://script.aculo.us/downloads and place the contents of /src in /usr/share/ebox/www/js/scriptaculous. No need to restart Apache or anything, just refresh the page. Thanks to bsccara for the fix.

52
Installation and Upgrades / Re: Auto Restart and Auto Shutdown
« on: July 26, 2010, 01:55:19 pm »
Run crontab -e to setup a crontab if you don't wanna worry about making executable cron.daily or other files in those directories. Crontab is really easy to use and a wonderful way to schedule things. An example would be, if you want it to reboot every minute of every hour of every day of every week of every month, then you would do this:

Code: [Select]
* * * * * reboot

That's it.

The order is minute (1-60), hour (1-24), day of the month (1-31), month (1-12), day of the week (Sun through Sat), then your command. If you could setup your BIOS to power it on or if you have a machine on the network that could send a magic packet and wake it up over Ethernet, then that would work too.

53
We need to make this a sticky. This was a huge issue with me too. It's probably what happens when you upgrade from 1.4. MOSAiX, did you upgrade from Hardy to Lucid and from 1.4 to 1.5 like I did?

:: SOLUTION ::
Download http://script.aculo.us/downloads and place the contents of /src in /usr/share/ebox/www/js/scriptaculous. Thanks to bsccara for the fix.

54
I was just going to note that myself. Size-limits are very important if logs are going to get that big. I've always thought my 8GB logs were huge.

55
Installation and Upgrades / Re: Internet Explorer Support
« on: July 26, 2010, 01:18:19 pm »
Sounds like a very important feature and must've taken a lot of courage to make the post. Which versions of IE does it not work in? Besides a bunch of scripting and security errors, it worked fine for me. I was unable to login due to LDAP issues when I upgraded to 1.5, but the page is definitely displaying. I tested in IE 5.5, 6, 7, and 8. What are the issues you're having?

56
:: COMMENTS ::

I could've sworn I wrote a post on this myself from 4 days ago, but it's not there. I'm having issues with slapd too I think only because my log file was showing the ldapi connection couldn't happen. Then I did purge samba and purge slapd as well as rm -rf /var/lib/ldap* && sudo rm -rf /etc/ldap/*. Now my log shows this:

Code: [Select]
2010/07/26 05:47:24 ERROR> Ldap.pm:721 EBox::Ldap::_errorOnLdap - Unknown error at EBox::UsersAndGroups::listSlaves invalid DN
2010/07/26 05:47:42 ERROR> Ldap.pm:719 EBox::Ldap::_errorOnLdap - $VAR1 = {
          'base' => 'ou=Groups,',
          'attrs' => [
                       'cn',
                       'gidNumber',
                       'description'
                     ],
          'filter' => '(objectclass=*)',
          'scope' => 'one'
        };
2010/07/26 05:47:42 ERROR> Ldap.pm:721 EBox::Ldap::_errorOnLdap - Unknown error at EBox::UsersAndGroups::groups invalid DN
2010/07/26 05:50:02 ERROR> Ldap.pm:719 EBox::Ldap::_errorOnLdap - $VAR1 = {
          'base' => 'ou=slaves,',
          'filter' => '(objectClass=slaveHost)',
          'scope' => 'sub'
        };
2010/07/26 05:50:02 ERROR> Ldap.pm:721 EBox::Ldap::_errorOnLdap - Unknown error at EBox::UsersAndGroups::listSlaves invalid DN
2010/07/26 05:55:03 ERROR> Ldap.pm:719 EBox::Ldap::_errorOnLdap - $VAR1 = {
          'base' => 'ou=slaves,',
          'filter' => '(objectClass=slaveHost)',
          'scope' => 'sub'
        };
2010/07/26 05:55:03 ERROR> Ldap.pm:721 EBox::Ldap::_errorOnLdap - Unknown error at EBox::UsersAndGroups::listSlaves invalid DN
2010/07/26 06:00:03 ERROR> Ldap.pm:719 EBox::Ldap::_errorOnLdap - $VAR1 = {
          'base' => 'ou=slaves,',
          'filter' => '(objectClass=slaveHost)',
          'scope' => 'sub'
        };
2010/07/26 06:00:03 ERROR> Ldap.pm:721 EBox::Ldap::_errorOnLdap - Unknown error at EBox::UsersAndGroups::listSlaves invalid DN

:: SOLUTION ::

I completely forgot though, issac gave me some things to run a long time ago which I still have saved in a text file, those are:

Code: [Select]
/usr/share/ebox-usersandgroups/ebox-usersandgroups-reinstall
/usr/share/ebox/ebox-unconfigure-module samba
/usr/share/ebox/ebox-unconfigure-module mail

The reinstall should fix everything. I've seen a recent ticket marked as solved when that was run to fix it and did it myself just now. I only wish there way a way to export and import lists of users to make this whole process easier.

57
:: MORE INFORMATION ::
The problem occurs by putting a pound sign (#) at the end of the URL. A similar problem occurs when at https://ebox.local/ebox/UsersAndGroups/Users if there's an error screen and you click "Go back". It only changes the URL to https://ebox.local/ebox/UsersAndGroups/Users#.

Sometimes it works, sometimes it doesn't. When it does not work, it is before I've hit the browser's back button. After going forward, the page works as it should. The Dashboard has no such workaround though.

58
eBox 1.5.8
2.6.32-24-generic-pae

:: BACKGROUND ::
This machine has been upgraded from 1.2, 1.3, 1.4, and now on 1.5. After the upgrade, the Networking module wasn't working but I fixed that. On the other hand, I'm still unable to get the LDAP/Samba stuff working so this might be related to me having a messed up setup on this particular machine.

:: PROBLEM ::
When clicking "Configure Widgets", the entire Dashboard locks up and only until a refresh am I able to click on anything.

:: TROUBLESHOOTING ::
I tested this on another eBox 1.5.8 machine which was installed with 1.5-1, and it does not have this problem.

59
eBox 1.5.8
2.6.32-24-generic-pae

:: QUESTION 1 ::

Am I able to just connect to an AD server and forgo the whole LDAP ordeal or is LDAP used as the method of transport of users and that's why all of these problems are occurring?

:: QUESTION 2 ::

What is the exact reason LDAP + Samba doesn't work? Since LDAP uses Samba users for authentication, I can't understand why they don't go together.

:: QUESTION 3 ::

If there were some way to not transfer users, but have an AD eBox server and have other computers authenticate into it, would that allow for Samba file sharing to work? Would it allow for any AD BDC computers in this way?

60
I fixed the network module, only Samba and LDAP don't work now. I did a purge of them, no fix. The only fix is probably the dreaded purging of eBox completely which I'm opposed to. Maybe there's an easier way? Haha.

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