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 - peterr

Pages: [1] 2 3 ... 5
I have just gone back to playing around with event monitoring and have rss and jabber up and running.
Rss was fine to set up once I figured  out the address you enter as channel link, in the config, was not the address you use to access the feed. A little comment in the help link might have been useful but it became obvious when I pressed the syndicate button (on the basis of 'I wonder what that does?').

Jabber was more of a challenge!
I started out trying to use an existing user on our google apps domain - no luck as you enter a server name and user name but eBox then assumes the jabber id is user_name@server_name when it is user_name@domain_name.
Next try, I installed the Jabber server and tried to subscribe a user specific for the server (I have failed at this before but thought I would give it another go)
So I then activated jabber for a user and set them as the sender of alerts to me, at my google apps address - nothing came through even though jabber is set to use other servers.
Finally I activated a jabber account for me and had alerts sent to that - works if I am on site, which is fine.

Now I am left with 2 problems (the point of this post)
The state monitor is constantly sending out 'ebox up and running' messages - is there any way to stop them and have it only send out messages when it is in the process of shutting down (eg UPS has run down)? For now I am turning this one off.
I also tried the system load monitor - that drove me mad!!
I added a new threshold and entered 0.6 in the box Warning maximum: thinking that I could easily push the server over this to test it out. I was expecting 'If the value is greater than this value and less than failure maximum a warn event is sent' to mean I would be alerted if the system load went over 0.6. What I got was a constant stream of messages telling me the load was below the Warning maximum - not what I wanted at all.
The fee disk space watcher does not keep telling me I have space left - I only get a warning when I run out of space, which is what I want and expected to happen.

Any Ideas on fixing the threshold settings or am I doing something wrong with them?
Could the state monitor be selective about what it sends out?

Installation and Upgrades / Re: No Antivirus Tab on File Sharing
« on: May 10, 2010, 02:45:13 pm »
on a system running 1.4.3 I have just installed samba shares and antivirus - still no samba-vscan package gets installed so you have to do it yourself.

Installation and Upgrades / Re: UserCorner refused connection
« on: February 27, 2010, 07:44:13 pm »
I have no idea as the logs contained nothing relating to the problem (as far as I could see). Currently I do not have this problem so I have no idea why I have lost it and you are now suffering.
What modules do you have with the server that is giving you the problem?
Mine (without problem) has nothing depending on users and groups and then things like network, firewall, events, logs, monitor and software management. It is basically just a web server that also acts as a master ldap for 2 other servers but, as master, has user corner activated.

Installation and Upgrades / Re: UserCorner refused connection
« on: February 26, 2010, 10:55:39 am »
yes, the updates fixed it and I am now on version 1.4 and do not have the problem there either.
What version are you currently using?

Installation and Upgrades / Re: ( Solved ) Help with voip
« on: February 12, 2010, 09:31:23 am »
I had the same issue with ebox 1.3 but never got meetings to work even with the ebox kernel. Now on 1.4 I have the same problem.  Interestingly I have 3 ebox servers running at the moment - all say they are fully up to date.
2 of them, a web server and the asterisk/jabber server, are running with the 2.6.24-27-server kernel and the samba server is using the 2.6.24-26-ebox kernel - ironic that the one that really needs the ebox kernel is not using it and one that probably does not is using it!  Or maybe the samba/PDC does need the ebox kernel and is smart enough to know it while asterisk also needs it but is not smart enough to realize.
I don't really understand why 3 up to date servers would be running different kernels though - admittedly the web server was installed on top of an existing lamp server but the other 2 both used the ebox iso yet one sticks with an ebox kernel and one does not.

Installation and Upgrades / Re: samba failure on 1.4
« on: February 12, 2010, 06:52:53 am »
Saturn2888 - no unfortunately your fix did not work for me, hence my reinstall

Phillmills - sorry to hear you came unstuck too!
As my failed samba server was a slave I got all my users and groups back again when I reinstalled and the new install did its first sync with the master - obviously shares and printers won't get included in this.
The other issue is that existing users who sync across do so before you are able to set up the file share so they default to a quota of 0 (ie no limit) so if you are expecting to limit you users to share space that will need to be put back.
I have yet to try it out but what about the ebox backup? Mind you it might take more than you want over, I suppose, and restore a broken setup up

Installation and Upgrades / Events - Jabber subscription failed
« on: February 11, 2010, 12:37:40 pm »
I have running jabber server and two other ebox servers and I want to enable the event dispatcher to IM any events that occur.
I tied setting up the dispatcher with an existing ebox user but the messages come from that user with no indication which server they relate to.  So I chaged teh settings to use a user related to the server e.g. admin.web or then I ticked the box - subscribe
The jabber server name is set the name of my server
The port is set to 5222 - that worked with a existing user
I filled in a password
and saved the settings
When I activated the jabber event dispatcher it told me 'subscription failed'

Any idea why?

Jabber is set up with ssl optional

Installation and Upgrades / Re: samba failure on 1.4
« on: February 11, 2010, 12:25:01 pm »
No luck

Part of the problem (I guess) is that when I installed ebox on this server I used the simple install - this did not format the hard drive (not that I realised that at the time) but while trouble shooting this I found some of my old samba shares still present.
Samba failed with them - I deleted them, it still failed. I tried stripping out all ebox software, settings and related folder and reinstalled.
In the end I reinstalled the whole lot but used the expert mode and deleted all the partitions and recreated them.

That finally fixed it

Installation and Upgrades / Re: samba failure on 1.4
« on: February 09, 2010, 10:40:22 am »
My users can not become admins on any group folders as I can not create group folders (I get the error I printed earlier).
A user can not become a samba user with admin rights as I get the other error I printed earlier
After a complete reinstall today it is still not working
My users sync with the master without problems it is just that the file share is totally broken
All I have is the samba server (showing up in the correct workgroup) that contains two shared folders that I can see ebox-internal-backups and ebox-quarantine plus any I create seperatly to the group ones or the users own folders.
The folder I have created has readonly access rights for all users. I am in a group with admin rights on it and I just gave myself read write access to it - can't enter the folder (it is in home/samba/shares)
Changing my access right to admin still does not let me in.
Interestingly there are no folders under /home/samba/users though so that is worth looking into

Installation and Upgrades / Re: samba failure on 1.4
« on: February 08, 2010, 01:03:45 pm »
Thanks for the suggestion, unfortunately it did not work - still exactly the same problem

Installation and Upgrades / Re: ldap passwords and master/slave
« on: February 06, 2010, 08:23:49 pm »
Yes, but the upgrade did not go well even with the help of the doc detailing how to do it (forget where it is) so I reinstalled from scratch.
Master slave seems to be working fine but some other bits are not (e.g samba) and I have yet to test the PDC or linux authentication (rather wanted ot get samba going first)

Installation and Upgrades / samba failure on 1.4
« on: February 05, 2010, 10:04:13 am »
I was trying to upgrade from 1.3 to 1.4 but gave up and just reinstalled.
I have a working master and two working slaves - yesterday I set up file sharing on one slave, all seemed to go well and I got as far as creating a share with one group having read-only access and another group having administrator rights.
Today I started to find the problems - I then found there was a samba update available so I installed that this morning and started checking what did or did not work.
On my linux computer I have my username and password stored in my samba settings - this used to let me browse the folders on the old ebox server (those I was allowed to anyway).
Now I can enter the samba server but can not access the share I created (I am in the group with admin rights and also in the read-only groups) and I can not see my own shared folder. I get prompted for a username and password - entering my username and password does not give me access.
Looking in my user settings (on the ebox server) I noticed I do not have administrator rights on PDC/file share so I ticked the box and clicked change
Code: [Select]
A really nasty bug has occurred
Unknown error at EBox::UsersAndGroups::addUserToGroup Referral received
Unknown error at EBox::UsersAndGroups::addUserToGroup Referral received at /usr/share/perl5/EBox/ line 712
EBox::Ldap::_errorOnLdap('Net::LDAP::Modify=HASH(0xa91d38c)', 'HASH(0xa8cb77c)') called at /usr/share/perl5/EBox/ line 373
EBox::Ldap::modify('EBox::Ldap=HASH(0xa7044b0)', 'cn=Domain Admins,ou=Groups,dc=web,dc=dcmc', 'HASH(0xa8cb77c)') called at /usr/share/perl5/EBox/ line 1732
EBox::UsersAndGroups::addUserToGroup('EBox::UsersAndGroups=HASH(0xa08fadc)', 'peter.roots', 'Domain Admins') called at /usr/share/perl5/EBox/ line 844
EBox::Samba::setAdminUser('EBox::Samba=HASH(0x9a3efe0)', 'peter.roots', 'yes') called at /usr/share/perl5/EBox/CGI/Samba/ line 79
EBox::CGI::Samba::ActiveSharing::_user('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/Samba/ line 86
EBox::CGI::Samba::ActiveSharing::_process('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/ line 262
EBox::CGI::Base::run('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/ line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Samba/ActiveSharing', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xa90d1c4)') called at /usr/lib/perl5/ModPerl/ line 204
eval {...} called at /usr/lib/perl5/ModPerl/ line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xa84e7f0)') called at /usr/lib/perl5/ModPerl/ line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xa84e7f0)') called at /usr/lib/perl5/ModPerl/ line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xa90d1c4)') called at -e line 0
eval {...} called at -e line 0
Currently I have no shares other than the one I created under filesharing>shares so I went to userandgroups>groups and tried to edit a group (created on the master before I set up the file share slave). One group is for everyone and the others are more limited - the attempt to edit any group (wanted to add a file share to each one) gave this
Code: [Select]
A really nasty bug has occurred
Can't call method "get_value" on an undefined value
Can't call method "get_value" on an undefined value at /usr/share/perl5/EBox/ line 740.
So basically samba is not working properly - to the extent of being able to see the server and some shared folders but that is about it, can't enter any of them.
Any ideas where to go next?
All 3 servers are up to date as of this morning

Installation and Upgrades / Re: 1.4 LDAP Master/Slave configuration
« on: February 05, 2010, 09:45:29 am »
did you include ebox-usersandgroups in your install?  The ldap master/slave settings appear on the GUI under users and groups - until you configure master/slave settings you will just have an option 'mode'
After you have set up mode you will then have the full usersandgroups setting menus and mode will no longer be available.

Installation and Upgrades / Re: 1.4-rc1 install failure
« on: February 02, 2010, 01:46:49 pm »
Thanks, I will give it a go.
Oh the page won't load
Ah, it does if I use http not https
Right here I go....

Installation and Upgrades / Re: 1.4-rc1 install failure
« on: February 02, 2010, 01:23:16 pm »
Here goes
Code: [Select]
peter@web:~$ sudo slapcat | grep -i master
[sudo] password for peter:
dn: cn=master,dc=web,dc=dcmc
objectClass: masterHost
structuralObjectClass: masterHost
cn: master
Then, also the master
Code: [Select]
peter@web:~$ sudo ls -l /etc/ldap/ssl/
ls: cannot access /etc/ldap/ssl/: No such file or directory
So, am I missing something vital there?
And finally
Code: [Select]
peter@web:~$ sudo netstat -ltnp | grep slap
tcp        0      0   *               LISTEN      4720/slapd
tcp6       0      0 :::389                  :::*                    LISTEN      4720/slapd
Now from the failing slave
Code: [Select]
administrator@eboxcomms:~$ sudo ls -l /etc/ldap/ssl/
[sudo] password for administrator:
total 12
lrwxrwxrwx 1 root     root       42 2010-02-02 14:22 masterldapca.pem -> /var/lib/ebox/conf/ssl-ca/masterldapca.pem
-r-------- 1 openldap openldap  798 2010-02-02 14:02 ssl.cert
-r-------- 1 openldap openldap  887 2010-02-02 14:02 ssl.key
-r-------- 1 openldap openldap 1685 2010-02-02 14:02 ssl.pem
And for the sake of completeness the working slave (on 1.3.16)
Code: [Select]
administrator@eboxoffice:~$ sudo ls -l /etc/ldap/ssl/
[sudo] password for administrator:
ls: cannot access /etc/ldap/ssl/: No such file or directory
So looks like something wrong with certificates that does not present a problem with the earlier version, how do I get out of this?

Pages: [1] 2 3 ... 5