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 / Zentyal Samba 3.2
« on: December 06, 2013, 08:25:43 pm »
After purging z3.2 samba, dns and users and setting everything back up again. I continue to get these errors in the samba log.
I thought this should have been fixed by now?
Code: [Select]
single_terminate: reason[ldapsrv_call_loop: tstream_read_pdu_blob_recv() - NT_
STATUS_CONNECTION_DISCONNECTED]
[2013/12/06 13:57:34.469778, 3] ../lib/ldb-samba/ldb_wrap.c:320(ldb_wrap_connec
t)
ldb_wrap open of secrets.ldb
[2013/12/06 13:57:34.472403, 3] ../source4/auth/ntlm/auth.c:270(auth_check_pass
word_send)
auth_check_password_send: Checking password for unmapped user []\[]@[(null)]
auth_check_password_send: mapped user is: []\[]@[(null)]
[2013/12/06 13:57:34.475485, 3] ../source4/smbd/service_stream.c:66(stream_term
inate_connection)
Terminating connection - 'ldapsrv_call_loop: tstream_read_pdu_blob_recv() - NT
_STATUS_CONNECTION_DISCONNECTED'
[2013/12/06 13:57:34.475697, 3] ../source4/smbd/process_single.c:114(single_ter
minate)
single_terminate: reason[ldapsrv_call_loop: tstream_read_pdu_blob_recv() - NT_
STATUS_CONNECTION_DISCONNECTED]
[2013/12/06 13:57:35.292607, 4] ../source3/smbd/sec_ctx.c:316(set_sec_ctx)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2013/12/06 13:57:36.189369, 4] ../source4/dsdb/repl/drepl_notify.c:463(dreplsr
v_notify_schedule)
dreplsrv_notify_schedule(5) scheduled for: Fri Dec 6 13:57:41 2013 EST
[2013/12/06 13:57:41.198498, 4] ../source4/dsdb/repl/drepl_notify.c:463(dreplsr
v_notify_schedule)
dreplsrv_notify_schedule(5) scheduled for: Fri Dec 6 13:57:46 2013 EST
[2013/12/06 13:57:45.790030, 3] ../lib/ldb-samba/ldb_wrap.c:320(ldb_wrap_connec
t)
ldb_wrap open of secrets.ldb
[2013/12/06 13:57:46.207765, 4] ../source4/dsdb/repl/drepl_notify.c:463(dreplsr
v_notify_schedule)
dreplsrv_notify_schedule(5) scheduled for: Fri Dec 6 13:57:51 2013 EST
[2013/12/06 13:57:47.356556, 3] ../source4/smbd/service_stream.c:66(stream_term
inate_connection)
Terminating connection - 'ldapsrv_call_loop: tstream_read_pdu_blob_recv() - NT
_STATUS_CONNECTION_DISCONNECTED'
[2013/12/06 13:57:47.356907, 3] ../source4/smbd/process_single.c:114(single_ter
minate)
single_terminate: reason[ldapsrv_call_loop: tstream_read_pdu_blob_recv() - NT_
STATUS_CONNECTION_DISCONNECTED]
[2013/12/06 13:57:48.064712, 4] ../source3/smbd/sec_ctx.c:316(set_sec_ctx)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0I thought this should have been fixed by now?
2
Installation and Upgrades / DNS Forwarding on Zentyal 3.2
« on: December 05, 2013, 01:53:15 am »
Has anyone successfully been able to setup DNS forwarding?
I recently upgraded from Ubuntu 10.04 to 12.04 and Z2.2 to Z3.2; I have yet to get DNS forwarding to work. The server I'm working with is a simple file server that is used to store backups on. It has two NIC's; I've tried setting both of them as DHCP and setting one to DHCP and one static. With IP addresses 192.168.1.205 and 192.168.1.206. The DNS server is setup on a different server running Ubuntu 10.04 Z2.2 with IP address 192.168.1.201. I've tried adding this IP <192.168.1.201> as a forwarder with no success. I've set transparent cache to enabled and disabled. I've added the DNS server as a hostname with it's appropriate IP address and listed it as a name server and still no luck. If I manually stop the zentyal DNS service and allow the bind service to run, it works without any problems. This is leading me to believe that the latest Z3.2 DNS module along with the Z3.2 Samba module is currently flawed.
I recently upgraded from Ubuntu 10.04 to 12.04 and Z2.2 to Z3.2; I have yet to get DNS forwarding to work. The server I'm working with is a simple file server that is used to store backups on. It has two NIC's; I've tried setting both of them as DHCP and setting one to DHCP and one static. With IP addresses 192.168.1.205 and 192.168.1.206. The DNS server is setup on a different server running Ubuntu 10.04 Z2.2 with IP address 192.168.1.201. I've tried adding this IP <192.168.1.201> as a forwarder with no success. I've set transparent cache to enabled and disabled. I've added the DNS server as a hostname with it's appropriate IP address and listed it as a name server and still no luck. If I manually stop the zentyal DNS service and allow the bind service to run, it works without any problems. This is leading me to believe that the latest Z3.2 DNS module along with the Z3.2 Samba module is currently flawed.
3
Installation and Upgrades / How To: Making a Zentyal User a System User
« on: December 04, 2013, 01:24:58 pm »
How To: Making a Zentyal User a System User
This came about from an unfortunate incident when upgrading my Z2.2 to Z3.2. I didn’t follow the documentation where I was supposed to export my users in 2.2 and prepare the output for import into 3.0 (in this case 3.2). My primary user on my linux server is the same user I use on my Windows PC. We all know if a system user already exists on the server you cannot add a user to Zentyal with the same name. I, like most people would like to have user id’s and password match so we don’t have to continue to enter our credentials to access our shares. This of course comes from working with the machines at home so security isn’t a huge deal. So basically I had to troubleshoot a better part of a day to figure out how to add my system user as a Zentyal user. I couldn’t just import the user into LDAP as I’ve done in the past with Z2.2 because the structure is entirely different. So here it is. This issue would typically be encountered when upgrading to the next major release of Zentyal or if your installing Zentyal on a vanilla Ubuntu install instead of using the actual Zentyal install discs. I hope this how to do helps you!
What to expect:
Digging in:
This came about from an unfortunate incident when upgrading my Z2.2 to Z3.2. I didn’t follow the documentation where I was supposed to export my users in 2.2 and prepare the output for import into 3.0 (in this case 3.2). My primary user on my linux server is the same user I use on my Windows PC. We all know if a system user already exists on the server you cannot add a user to Zentyal with the same name. I, like most people would like to have user id’s and password match so we don’t have to continue to enter our credentials to access our shares. This of course comes from working with the machines at home so security isn’t a huge deal. So basically I had to troubleshoot a better part of a day to figure out how to add my system user as a Zentyal user. I couldn’t just import the user into LDAP as I’ve done in the past with Z2.2 because the structure is entirely different. So here it is. This issue would typically be encountered when upgrading to the next major release of Zentyal or if your installing Zentyal on a vanilla Ubuntu install instead of using the actual Zentyal install discs. I hope this how to do helps you!
What to expect:
- Back everything you want up!!! I can’t stress this enough.
- Prepare to remove your system user from the server, yes it sounds strange but this is what needs to be done.
- All commands will require root privileges, you are adding users and modifying system files; so…
- Be familiar with linux CLI. This can be accomplished by the average novice but it may require some reading up on some things to get a full understanding as to what is happening.
- Prepare to be busy for quite some time. I did all of this by logging into the server from my Windows PC and SSH. It can be done locally at the server of course.
Digging in:
- Change directory to /home and identify your home directory. Back it up, I renamed by using the command mv /home/james /home/james1
- Create a new user using useradd, this will be a temporary account so you can actually work with things. I created the one with username as “test”, it didn’t matter because I’m going to blow away the user once I’m done.
- Setup the new users password to be the same as your system password: `passwd test` and follow the prompts. I’ll explain why in a short while
- Add the new user to the admin and sudoers groups. If you don’t do this you won’t be able to continue; `sudo adduser <username> sudo` and `sudo adduser <username> admin`
- Logoff the system and ensure that your user id, the one you want to keep is NOT logged in whatsoever.
- Login to the server using the new user you’ve just added and become root `sudo –i`, it will prompt you for your password; it should be the same as the one of your system account.
- Now, delete your system account. What?
? Yup, delete your system account. It’s the only way to get this to work. You can do so by issuing the command `deluser <username>` - Now navigate to the Zentyal Web GUI and login using the temporary system user you just added. Why do you ask, Zentyal will only allow a system user the ability to login to its interface. It’s how they’ve setup their security, it can be changed but it does defeat the purpose.
- Now add your system account to Zentyal as a Zentyal user, we must do this first. You should be able to add it without any problems but it’s not guaranteed. Be prepared to google a LOT if you do run into problems.
- Now that you’ve added your account to Zentyal we will now add the account to the system, but we cannot do so by issuing the `useradd` command. It will complain that the user is already on the system; as I would expect that it would since you just added it to Zentyal. We will have to do this manually by touching each of the files listed below.
/etc/group
/etc/passwd
/etc/shadow - Open /etc/group in your favorite CLI editor, I like to use nano. Here we will identify all users that have been manually added to your system. Basically the last user should be the temporary user you added in the steps above and should be located at the bottom of the list. It’s UID (I believe it’s called the UID, not entirely sure at the moment) should be a numeric value four characters in length; i.e. ‘1000’. Add the your users, the one you just added to Zentyal to the bottom of this file copying the same structure as your temporary user but instead of copying the UID increment it by one so it would look like ‘1001’ instead of ‘1000’. Get it? This UID must be unique. Keep in mind, the UID you choose for your system account must match your username and be the same in all three files.
- Now open /etc/passwd and do the same thing as you did above. Following the structure and format of the file. Your temporary user should be located at the bottom of the list, copy the format and add your Zentyal user to it.
- Now open /etc/shadow and locate your temporary user. The user should be at the bottom of this list to. Remember when I said to set the same password as you are using for your system account? This is why, the temporary user has it’s password hashed; you’ll see a bunch of character after the temporary username. I suggest copying the entire line and appending it to the bottom of the file and then changing the name to match your system user.
- Navigate to /home, remember when I said to back up your system home directory? We will now restore it, that’s if you change the directory name; if all you did is backup your files instead then you won’t have to create a new /home directory or rename it. Attempt to change the ownership to your new system account. It should work.
- Open a terminal account and attempt to SSH into your server using your new system account using the same password as your temporary user. Did it work? I hope so, otherwise you have to do a bit of troubleshooting; reviewing the steps to see if you missed something.
- Now try to login locally to the server. If you’re logged in using the temporary account logout and attempt login using your system account. Did it work? I hope so.
- Log back off and login using your temporary account. We will now add your new system account to the admin and sudoers groups. Zentyal Web GUI requires that the system account be members of those groups. Do this by following step number 4.
- So we should be all set, just two more things and then some cleanup. Restart Zentyal users and webadmin services by issuing these commands: `/etc/init.d/zentyal users restart` and /etc/init.d/zentyal webadmin restart`.
- Navigate to Zentyal Web GUI and you should now be able to login using your system account. Now setup your share folder and access it from another PC. If all went well, you can safely delete the temporary account created.
4
Installation and Upgrades / Migrate Zentyal 2.2 > 3.2
« on: December 02, 2013, 02:24:08 pm »
Has anyone attempted to migrate from Zentyal 2.2 to 3.2 yet? Or to any of the interim releases in between? It's been a while since I've been on this forum and I've postponed my migration for the longest time. I have three weeks of vacation coming up and I think this is the best time for me to do this. The thing is I have four servers to upgrade and one of them is remote (approx 180 miles away).
All servers are running Ubuntu 10.04 with the latest updates. My high level plan is the following for all four servers with some additional nuances for each server, such as moving the DHCP and DNS server from one to another.
I will attempt to use the 2.2 > 3.0 export/import scripts but they may not be required, as I mentioned above. The users configured aren't that critical since I know the password and don't have more than 10 users on the system. I will most likely export the LDAP and import it again if needed (probably unlikely because the current zentyal configuration will be wiped out and reinstalled).
I guess my primary question is, has anyone attempted such a drastic migration?
All servers are running Ubuntu 10.04 with the latest updates. My high level plan is the following for all four servers with some additional nuances for each server, such as moving the DHCP and DNS server from one to another.
- Identify important customized configurations, i.e. zentyal hooks and crontab entries.
- Export LDAP configurations, which is totally critical because the server support mininal users
- Upgrade Distro to 12.04
- Install Zentyal 3.2 and only required modules for each servers operational needs
I will attempt to use the 2.2 > 3.0 export/import scripts but they may not be required, as I mentioned above. The users configured aren't that critical since I know the password and don't have more than 10 users on the system. I will most likely export the LDAP and import it again if needed (probably unlikely because the current zentyal configuration will be wiped out and reinstalled).
I guess my primary question is, has anyone attempted such a drastic migration?
5
Installation and Upgrades / [SOLVED] Unable to Enable Users Module in Zentyal 2.2
« on: September 07, 2012, 01:58:01 pm »Quote
Ticket# 5018
***I'm hoping that someone will have some type of an idea***
I attempted to migrate ebox 2.0 to zentyal version 2.2 but the migration script failed. I then proceeded to install zentyal 2.2 manually and have been able to setup all other required modules but the users and file sharing. I encounter this error when trying to enable the users module. This is the second time attempting to reinstall the module using this command '/usr/share/zentyal-users/reinstall' from ticket http://trac.zentyal.org/ticket/3838
*Error below* Failed to enable: root command set -e auth-client-config -a -p ebox auth-client-config -a -p ebox -r auth-client-config -t nss -p ebox failed. Error output: Error in resetting 'nss': No previous settings found in current file -- Errors found. Aborting (no changes made) Command output: . Exit value: 1
Error
Failed to enable: root command set -e
auth-client-config -a -p ebox
auth-client-config -a -p ebox -r
auth-client-config -t nss -p ebox failed.
Error output: Error in resetting 'nss': No previous settings found in current file
--
Errors found. Aborting (no changes made)
Command output: .
Exit value: 1
Trace
Failed to enable: root command set -e
auth-client-config -a -p ebox
auth-client-config -a -p ebox -r
auth-client-config -t nss -p ebox failed.
Error output: Error in resetting 'nss': No previous settings found in current file
--
Errors found. Aborting (no changes made)
Command output: .
Exit value: 1 at /usr/share/perl5/EBox/CGI/ServiceModule/ConfigureModuleController.pm line 74
EBox::CGI::ServiceModule::ConfigureModuleController::_process('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0x25...') called at /usr/share/perl5/EBox/CGI/Base.pm line 275
EBox::CGI::Base::run('EBox::CGI::ServiceModule::ConfigureModuleController=HASH(0x25...') called at /usr/share/perl5/EBox/CGI/Run.pm line 129
EBox::CGI::Run::run('EBox::CGI::Run', 'ServiceModule/ConfigureModuleController', 'EBox') called at /usr/share/zentyal/cgi/ebox.cgi line 34
ModPerl::ROOT::ModPerl::Registry::usr_share_zentyal_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0x26c2f458)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x26c0a3a8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x26c0a3a8)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x26c2f458)') called at -e line 0
eval {...} called at -e line 0
- Purged all Zentyal modules and rebooted server
- Selected zentyal-core, users and samba from the list of packages to install. This was to keep things minimal as I work through the issues
- Installed libnss-ldapd and libpam-ldapd instead of libnss-ldap libpam-ldap
- Imported backed up LDIF from zentyal 2.0 configuration using a plugin in Eclipse
- Updated ldap password form the new one that was installed after purging the modules earlier
- Was able to add and remove users but was unable to access any shares. Every attempt prompted for a user name and password
- Replaced libnss-ldapd and libpam-ldapd with libnss-ldap libpam-ldap and removed nslcd package
- Updated sid with /usr/share/zentyal-users/fix-sid and restarted zentyal users, zentyal samba and winbind services
- After the above steps, the user shares were accessible, I finished setting up the DHCP and DNS modules to complete the installation
- Also noted that in order to have thin client allow the selection of a group object or a range of IP addresses the zentyal ftp package must be installed
All this took me the better part of four night working minimally 4 hours each night; I got very little sleep
I do hope this info helps someone since a number of the steps I used came from numerous forum threads and tickets which don't appear to be completely resolved.
6
Installation and Upgrades / Upgrade Zentyal 2.0 to 2.2 Remotely
« on: August 27, 2012, 11:51:13 am »
As the subject says, Upgrade Zentyal 2.0 to 2.2 Remotely. Is it feasible? Has anyone attempted it? I have a server which I monitor a couple of hundred miles a way and the likely hood that I'm going to visit to upgrade it any time soon is slim to none. I'd like to upgrade it before Zentyal 3.0 is out. I've only successfully upgrade one server from 2.0 to 2.2 and that was done locally.
7
Installation and Upgrades / [SOLVED] Zentyal DDNS Problems?
« on: August 08, 2012, 06:51:05 pm »
Does anyone know if there is a DDNS problem with Zentyal and the domain servers. My cable modem experienced a problem yesterday and was down for multiple hours. Once I resolved that issue, it was handed a new IP address. This new IP address is correctly presented in the Zentyal subscription page but when I perform an NSLOOKUP from the command line, my old IP address is resolved. This is preventing all of my remote servers to connect to my servers through VPN.
My server has all the latest updates and Zentyal updates that have been made available.
My server has all the latest updates and Zentyal updates that have been made available.
8
Installation and Upgrades / [SOLVED] Zentyal DDNS Not Working?
« on: June 03, 2012, 08:11:51 pm »
Does anyone know or is anyone having issues with Zentyal's DDNS? My servers are unable to resolve there names resulting in VPN connection issues.
9
Installation and Upgrades / TLS Error: local/remote TLS keys are out of sync
« on: March 31, 2012, 02:46:45 pm »
On one of my four zentyal servers keeps getting "TLS Error: local/remote TLS keys are out of sync" error while being connected to the Zentyal Cloud Services. I have not made any changes to this servers openvpn configuration. Is there something I need to update? Provide further information? Is anyone else getting this same error? I was only made aware of this because of the email alert I receive from Zentyal informing me my server disconnected.
10
Installation and Upgrades / [SOLVED] Migration tool beta 2.0 to 2.2 failed leaving server "crippled"
« on: October 05, 2011, 08:33:51 pm »
Here's my situation...
I attempted the beta script to migrate zentyal 2.0 to 2.2... and so my troubles begin.
During the migration process I was presented with an install issue where zarafa couldn't be installed so I exited the script (big mistake) and was able to somehow install zarafa. I attempted to start the script again but it ended because ebox and its configurations were no longer present and zentyal was already installed. I decided to review the script and manually walk through it. I determined that I was at the point of running the post-upgrade scripts, so I ran those first and all seemed well. I tried starting zentyal and ran into this problem:
Sorry, an unexpected error has occurred
Can't call method 'valueByName' on an undefined value
Show technical details
Report the problem
Trace
Can't call method "valueByName" on an undefined value at /usr/share/perl5/EBox/Network.pm line 2257.
I then decided to remove zentyal and ldap (purge) and re-install. I'm stuck at trying to enable the file sharing module. Zentyal module users is enabled and I do see the users that were previously configured. I believe it has something to do with ldap and zentyal trying to connect using slapd because I've attempted to restore my original samba config using the restore configuration command in /usr/share/zentyal. I've edited the /etc/default/ldap configuration so that the service can now start but it terminates unexpectedly, this is what's in my syslog.
Oct 5 14:26:45 proteus slapd[1903]: config error processing olcDatabase={2}hdb,cn=config: <olcSuffix> namingContext "dc=proteus,dc=us,dc=nss,dc=net" already served by a preceding hdb database
Oct 5 14:26:45 proteus slapd[1903]: slapd stopped.
Oct 5 14:26:45 proteus slapd[1903]: connections_destroy: nothing to destroy.
Oct 5 14:26:45 proteus init: ebox.slapd main process (1903) terminated with status 1
Oct 5 14:26:45 proteus init: ebox.slapd main process ended, respawning
Most likely case, it is not able to connect correctly.
My question is, how would I be able to reset this configuration and successfully setup file sharing again without removing/destroying the existing users information in Zentyal?
I attempted the beta script to migrate zentyal 2.0 to 2.2... and so my troubles begin.
During the migration process I was presented with an install issue where zarafa couldn't be installed so I exited the script (big mistake) and was able to somehow install zarafa. I attempted to start the script again but it ended because ebox and its configurations were no longer present and zentyal was already installed. I decided to review the script and manually walk through it. I determined that I was at the point of running the post-upgrade scripts, so I ran those first and all seemed well. I tried starting zentyal and ran into this problem:
Sorry, an unexpected error has occurred
Can't call method 'valueByName' on an undefined value
Show technical details
Report the problem
Trace
Can't call method "valueByName" on an undefined value at /usr/share/perl5/EBox/Network.pm line 2257.
I then decided to remove zentyal and ldap (purge) and re-install. I'm stuck at trying to enable the file sharing module. Zentyal module users is enabled and I do see the users that were previously configured. I believe it has something to do with ldap and zentyal trying to connect using slapd because I've attempted to restore my original samba config using the restore configuration command in /usr/share/zentyal. I've edited the /etc/default/ldap configuration so that the service can now start but it terminates unexpectedly, this is what's in my syslog.
Oct 5 14:26:45 proteus slapd[1903]: config error processing olcDatabase={2}hdb,cn=config: <olcSuffix> namingContext "dc=proteus,dc=us,dc=nss,dc=net" already served by a preceding hdb database
Oct 5 14:26:45 proteus slapd[1903]: slapd stopped.
Oct 5 14:26:45 proteus slapd[1903]: connections_destroy: nothing to destroy.
Oct 5 14:26:45 proteus init: ebox.slapd main process (1903) terminated with status 1
Oct 5 14:26:45 proteus init: ebox.slapd main process ended, respawning
Most likely case, it is not able to connect correctly.
My question is, how would I be able to reset this configuration and successfully setup file sharing again without removing/destroying the existing users information in Zentyal?
11
Installation and Upgrades / One of Zentyal Updates Broke Software Management
« on: June 18, 2011, 05:21:03 pm »
When I try to view the list of software updates for Zentyal I receive this error.
Can't call method "FileList" on an undefined value
To show technical details click here.
Trace
Can't call method "FileList" on an undefined value at /usr/share/perl5/EBox/Software.pm line 828.
I'm running Zentyal core version 2.0.20 with the latest stable packages available. This is occurring on all four of my Zentyal servers.
I've started using apt-get update && apt-get upgrade to install the latest updates for my servers with the hopes of seeing an update to the Software Management module.
Can't call method "FileList" on an undefined value
To show technical details click here.
Trace
Can't call method "FileList" on an undefined value at /usr/share/perl5/EBox/Software.pm line 828.
I'm running Zentyal core version 2.0.20 with the latest stable packages available. This is occurring on all four of my Zentyal servers.
I've started using apt-get update && apt-get upgrade to install the latest updates for my servers with the hopes of seeing an update to the Software Management module.
12
Installation and Upgrades / [SOLVED] Unable to connect to logs database
« on: June 18, 2011, 03:44:41 am »
I've been having this issue for quite some time. I've tried following a few posts to resolve it. I get the following error when I try to view the reports.
Trace
There wasn't a database connection, check if database exists\n at /usr/share/perl5/EBox/PgDBEngine.pm line 139
EBox::PgDBEngine::_disconnect('EBox::PgDBEngine=HASH(0xbab9d530)') called at /usr/share/perl5/EBox/PgDBEngine.pm line 665
EBox::PgDBEngine::DESTROY('EBox::PgDBEngine=HASH(0xbab9d530)') called at /usr/share/perl5/Error.pm line 408
EBox::CGI::Base::run('EBox::CGI::Logs::Index=HASH(0xbade6910)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Logs/Index', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 35
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xbab6ab90)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xb991e308)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xb991e308)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xbab6ab90)') called at -e line 0
eval {...} called at -e line 0
When I run the command `su postgres -c psql eboxlogs` at the terminal; it responds back with no output or any indication that the connection was successful or if the database exists.
I've made the attempt at recreating the database using the following commands.
sudo chsh -s /bin/bash postgres
sudo /usr/share/ebox/ebox-create-db eboxlogs
sudo chsh -s /bin/false postgres
Then adding the tables using this command `su postgres /usr/share/ebox/ebox-sql-table add [table NAME]` and all the sql files in the directory `/usr/share/ebox/sqllog`
`lsof | grep postgresql` does show that it is listening on the localhost.
I did notice that the port was set to 5433 instead of 5432 in pg_hba.conf and restarted both the ebox logs service and postgresql service. When I view the postgresql logs; all that is logged is this `FATAL: Ident authentication failed for user "ebox"`. It appears that ebox is unable to login. Perhaps this is some kind of password issue?
I've also tried re-installing the zentyal and postgresql packages by running `sudo apt-get install reinstall zentyal postgresql`.
Trace
There wasn't a database connection, check if database exists\n at /usr/share/perl5/EBox/PgDBEngine.pm line 139
EBox::PgDBEngine::_disconnect('EBox::PgDBEngine=HASH(0xbab9d530)') called at /usr/share/perl5/EBox/PgDBEngine.pm line 665
EBox::PgDBEngine::DESTROY('EBox::PgDBEngine=HASH(0xbab9d530)') called at /usr/share/perl5/Error.pm line 408
EBox::CGI::Base::run('EBox::CGI::Logs::Index=HASH(0xbade6910)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Logs/Index', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 35
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xbab6ab90)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xb991e308)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xb991e308)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xbab6ab90)') called at -e line 0
eval {...} called at -e line 0
When I run the command `su postgres -c psql eboxlogs` at the terminal; it responds back with no output or any indication that the connection was successful or if the database exists.
I've made the attempt at recreating the database using the following commands.
sudo chsh -s /bin/bash postgres
sudo /usr/share/ebox/ebox-create-db eboxlogs
sudo chsh -s /bin/false postgres
Then adding the tables using this command `su postgres /usr/share/ebox/ebox-sql-table add [table NAME]` and all the sql files in the directory `/usr/share/ebox/sqllog`
`lsof | grep postgresql` does show that it is listening on the localhost.
I did notice that the port was set to 5433 instead of 5432 in pg_hba.conf and restarted both the ebox logs service and postgresql service. When I view the postgresql logs; all that is logged is this `FATAL: Ident authentication failed for user "ebox"`. It appears that ebox is unable to login. Perhaps this is some kind of password issue?
I've also tried re-installing the zentyal and postgresql packages by running `sudo apt-get install reinstall zentyal postgresql`.
13
Installation and Upgrades / Server won't autobackup to Zentyal Cloud
« on: May 26, 2011, 02:45:22 pm »
I have the basic zentyal service. I have four of my servers connected but only three of them automatically back up their configurations to zentyal cloud. Is there a configuration parameter somewhere that needs to be checked?
14
Installation and Upgrades / Unable to connect to database
« on: November 25, 2010, 03:17:59 pm »
I recently began to receive this error when trying to view the firewall logs. I've attempted a reboot of the server and made sure postgresql was running. I'm current version is zentyal 2.0.7
Trace
There wasn't a database connection, check if database exists\n at /usr/share/perl5/EBox/PgDBEngine.pm line 139
EBox::PgDBEngine::_disconnect('EBox::PgDBEngine=HASH(0xbc6a0ec0)') called at /usr/share/perl5/EBox/PgDBEngine.pm line 644
EBox::PgDBEngine::DESTROY('EBox::PgDBEngine=HASH(0xbc6a0ec0)') called at /usr/share/perl5/Error.pm line 408
EBox::CGI::Base::run('EBox::CGI::Logs::Index=HASH(0xbc698df8)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Logs/Index', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 35
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xbc4f7370)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xbc5b5b58)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xbc5b5b58)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xbc4f7370)') called at -e line 0
eval {...} called at -e line 0
Trace
There wasn't a database connection, check if database exists\n at /usr/share/perl5/EBox/PgDBEngine.pm line 139
EBox::PgDBEngine::_disconnect('EBox::PgDBEngine=HASH(0xbc6a0ec0)') called at /usr/share/perl5/EBox/PgDBEngine.pm line 644
EBox::PgDBEngine::DESTROY('EBox::PgDBEngine=HASH(0xbc6a0ec0)') called at /usr/share/perl5/Error.pm line 408
EBox::CGI::Base::run('EBox::CGI::Logs::Index=HASH(0xbc698df8)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Logs/Index', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 35
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xbc4f7370)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xbc5b5b58)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xbc5b5b58)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xbc4f7370)') called at -e line 0
eval {...} called at -e line 0
15
Installation and Upgrades / ebox 1.4 unable to send mail events
« on: February 10, 2010, 04:23:57 am »
I was able to solve the master/slave issue I was having. The results are, two masters since I'm unable to configure a slave to an existing ebox master that has shares.
Since the mail module is dependent on the users and groups module, I'm just now able to configure it. The module is configure the same way as the other four server. two of which are working and the third isn't, no visible issues are seen in the logs. Below are the logs from the mail.log file.
Feb 9 22:19:02 calypso postfix/trivial-rewrite[12557]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix,dc=calypso,dc=us,dc=nss,dc=net' not found: 32: No such object
Feb 9 22:19:02 calypso postfix/trivial-rewrite[12557]: fatal: ldap:valiases(0,lock|fold_fix): table lookup problem
Feb 9 22:19:02 calypso postfix/trivial-rewrite[12558]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix,dc=calypso,dc=us,dc=nss,dc=net' not found: 32: No such object
Feb 9 22:19:02 calypso postfix/trivial-rewrite[12558]: fatal: ldap:valiases(0,lock|fold_fix): table lookup problem
Feb 9 22:19:03 calypso postfix/smtpd[10830]: warning: problem talking to service rewrite: Success
Feb 9 22:19:03 calypso postfix/cleanup[11035]: warning: problem talking to service rewrite: Connection reset by peer
Feb 9 22:19:03 calypso postfix/master[8458]: warning: process /usr/lib/postfix/trivial-rewrite pid 12557 exit status 1
Feb 9 22:19:03 calypso postfix/master[8458]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
Feb 9 22:19:03 calypso postfix/smtpd[11348]: warning: problem talking to service rewrite: Success
Feb 9 22:19:03 calypso postfix/master[8458]: warning: process /usr/lib/postfix/trivial-rewrite pid 12558 exit status 1
Feb 9 22:20:03 calypso postfix/trivial-rewrite[13288]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix,dc=calypso,dc=us,dc=nss,dc=net' not found: 32: No such object
Feb 9 22:20:03 calypso postfix/trivial-rewrite[13288]: fatal: ldap:valiases(0,lock|fold_fix): table lookup problem
Feb 9 22:20:03 calypso postfix/trivial-rewrite[13289]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix,dc=calypso,dc=us,dc=nss,dc=net' not found: 32: No such object
Feb 9 22:20:03 calypso postfix/trivial-rewrite[13289]: fatal: ldap:valiases(0,lock|fold_fix): table lookup problem
Feb 9 22:20:04 calypso postfix/smtpd[10830]: warning: problem talking to service rewrite: Success
Feb 9 22:20:04 calypso postfix/cleanup[11035]: warning: problem talking to service rewrite: Connection reset by peer
Feb 9 22:20:04 calypso postfix/master[8458]: warning: process /usr/lib/postfix/trivial-rewrite pid 13288 exit status 1
Feb 9 22:20:04 calypso postfix/master[8458]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
Feb 9 22:20:04 calypso postfix/master[8458]: warning: process /usr/lib/postfix/trivial-rewrite pid 13289 exit status 1
Feb 9 22:20:04 calypso postfix/smtpd[11348]: warning: problem talking to service rewrite: Success
Since the mail module is dependent on the users and groups module, I'm just now able to configure it. The module is configure the same way as the other four server. two of which are working and the third isn't, no visible issues are seen in the logs. Below are the logs from the mail.log file.
Feb 9 22:19:02 calypso postfix/trivial-rewrite[12557]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix,dc=calypso,dc=us,dc=nss,dc=net' not found: 32: No such object
Feb 9 22:19:02 calypso postfix/trivial-rewrite[12557]: fatal: ldap:valiases(0,lock|fold_fix): table lookup problem
Feb 9 22:19:02 calypso postfix/trivial-rewrite[12558]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix,dc=calypso,dc=us,dc=nss,dc=net' not found: 32: No such object
Feb 9 22:19:02 calypso postfix/trivial-rewrite[12558]: fatal: ldap:valiases(0,lock|fold_fix): table lookup problem
Feb 9 22:19:03 calypso postfix/smtpd[10830]: warning: problem talking to service rewrite: Success
Feb 9 22:19:03 calypso postfix/cleanup[11035]: warning: problem talking to service rewrite: Connection reset by peer
Feb 9 22:19:03 calypso postfix/master[8458]: warning: process /usr/lib/postfix/trivial-rewrite pid 12557 exit status 1
Feb 9 22:19:03 calypso postfix/master[8458]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
Feb 9 22:19:03 calypso postfix/smtpd[11348]: warning: problem talking to service rewrite: Success
Feb 9 22:19:03 calypso postfix/master[8458]: warning: process /usr/lib/postfix/trivial-rewrite pid 12558 exit status 1
Feb 9 22:20:03 calypso postfix/trivial-rewrite[13288]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix,dc=calypso,dc=us,dc=nss,dc=net' not found: 32: No such object
Feb 9 22:20:03 calypso postfix/trivial-rewrite[13288]: fatal: ldap:valiases(0,lock|fold_fix): table lookup problem
Feb 9 22:20:03 calypso postfix/trivial-rewrite[13289]: warning: dict_ldap_lookup: valiases: Search base 'ou=mailalias,ou=postfix,dc=calypso,dc=us,dc=nss,dc=net' not found: 32: No such object
Feb 9 22:20:03 calypso postfix/trivial-rewrite[13289]: fatal: ldap:valiases(0,lock|fold_fix): table lookup problem
Feb 9 22:20:04 calypso postfix/smtpd[10830]: warning: problem talking to service rewrite: Success
Feb 9 22:20:04 calypso postfix/cleanup[11035]: warning: problem talking to service rewrite: Connection reset by peer
Feb 9 22:20:04 calypso postfix/master[8458]: warning: process /usr/lib/postfix/trivial-rewrite pid 13288 exit status 1
Feb 9 22:20:04 calypso postfix/master[8458]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
Feb 9 22:20:04 calypso postfix/master[8458]: warning: process /usr/lib/postfix/trivial-rewrite pid 13289 exit status 1
Feb 9 22:20:04 calypso postfix/smtpd[11348]: warning: problem talking to service rewrite: Success
Pages: [1] 2