eBox 1.5: no access to user corner

[christian]

User corner now works after forced reinstallation (se my other post related to this).

so at least good news is that user corner works again.

[mparic]

What module was "forced reinstallation"? I'm running into the same "Internal Server Error" and found permission errors when user-corner tried to write to /var/lib/ebox/tmp. I changed the permissions in the tmp file to allow the ebox-usercorner user to write however now I'm getting the error:

[Sat Aug 07 00:15:52 2010] [error] [client 192.168.1.150] /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/OCCgHQKNCr.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo: no tty present and no askpass program specified\n, referer: https://ebox.home.office:8888/

[ARYIN]

My eBox is version 1.5.10.

Previously, my eBox user corner is not work if using master/slave setup.
Now I can't using it even there's no slave. The problem as mparic described.

Using 1.5.8 or 1.5.9 is work, I dun remember which one. I think Christian found reinstallation work bcoz he installs new update but not reinstallation. When updated to 1.5.10, the eBox usercorner failed again.

Today, I found there has an update of ebox-usersandgroups, which version is 1.5.5, I setup again but still no luck. The permission problem mparic described is gone. however,

Sudo.pm:216 EBox::Sudo::_rootError - root command auth-client-config -t pam-password pam-auth pam-session pam-account -p ebox -r failed.

this error is continue.

[lucaspr]

Same error here.

This has to be fixed, this is a real showstopper... anybody?

[mparic]

Other than letting the Users change their own passwords, the only other functionality I needed from  User Corner was creating external email account retrieval entries. Fortunately eBox just uses fetchmail for this so to get around the User Corner access issue I simply disabled User Corner, copied /etc/ebox-fetchmail.rc to /etc/fetchmailrc, entered the appropriate external account entries (found http://www.freebsd.org/doc/handbook/mail-fetchmail.html helpful), then started the fetchmail daemon by setting START_DAEMON=yes in /etc/default/fetchmail and 'sudo /etc/init.d/fetchmail start'. Would be a bit cumbersome for many accounts but could get you up and running until User Corner is fixed.

[lucaspr]

Other than letting the Users change their own passwords, the only other functionality I needed from  User Corner was creating external email account retrieval entries. Fortunately eBox just uses fetchmail for this so to get around the User Corner access issue I simply disabled User Corner, copied /etc/ebox-fetchmail.rc to /etc/fetchmailrc, entered the appropriate external account entries (found http://www.freebsd.org/doc/handbook/mail-fetchmail.html helpful), then started the fetchmail daemon by setting START_DAEMON=yes in /etc/default/fetchmail and 'sudo /etc/init.d/fetchmail start'. Would be a bit cumbersome for many accounts but could get you up and running until User Corner is fixed.

First I would like to thank you for this info! That was what I needed to get fetchmail running!

And second: You are absolutly right about this, a bit cumbersome if one would have a lot of accounts.. But still, a fix would be far better then this workaround (for me it's perfect! I've got my eBox-box running with zarafa and fetchmail!).

[DMoRiaM]

I am not quite sure if the problem is related but lets see.

I am running a standalone server here for test purposes and I got no access to the user corner as well (http://gdmserv01:8888 brings a Internal Server Error message). First I saw write permissions errors in /var/lib/ebox/tmp and did a chmod 777 there. The error changed.

Code: [Select]

Use of uninitialized value $reason in length at (eval 117) line 49.
sh: cannot create /var/lib/ebox/tmp/stderr: Permission denied

So a did a chmod -R 777 there:

Code: [Select]

[Thu Aug 12 10:07:32 2010] [error] [client 192.168.1.101] root command status 'ebox.redis' failed. \nError output: \nCommand output: . \nExit value: 2, referer: https://gdmlserv01:8888/
Use of uninitialized value $reason in length at (eval 135) line 49.
[Thu Aug 12 10:09:11 2010] [error] [client 192.168.1.101] /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/G4vWVthK3X.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo: no tty present and no askpass program specified\n, referer: https://gdmlserv01:8888/
[Thu Aug 12 10:10:07 2010] [error] [client 192.168.1.101] /usr/bin/sudo -p sudo: /var/lib/ebox/tmp/CmRNSM73Z1.cmd 2> /var/lib/ebox/tmp/stderr raised the following sudo error: sudo: no tty present and no askpass program specified\n, referer: https://gdmlserv01:8888/

Now I got that problem with no tty present and no askpass program specified...

Lets do a little more digging.

Embraces Widely Amplified
D'

[gwoollett]

With the absence of a working user corner I'm trying to get fetchmail running.
I'm running EBox 1.5 on UBuntu 10.04 x64.

I have a virtual mail domain called "wbc" with a user called "graemew"
Below is my /etc/fetchmailrc

# /etc/fetchmailrc for system-wide daemon mode
# This file must be chmod 0600, owner fetchmail

set daemon        120                # Pool every 5 minutes
set syslog                        # log through syslog facility
set postmaster  root

set no bouncemail                # avoid loss on 4xx errors
                                # on the other hand, 5xx errors get
                                # more dangerous...

##########################################################################
# Hosts to pool
##########################################################################

# Defaults ===============================================================
# Set antispam to -1, since it is far safer to use that together with
# no bouncemail
defaults:
timeout 300
antispam -1
batchlimit 100

poll pop.gmail.com protocol POP3 user "xxxxx" there with password "xxxxx" is graemew@wbc here ssl

this is my mail.log output when fetchmail runs


NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 504 5.5.2 <graemew@wbc>: Recipient address rejected: need fully-qualified address; from=<graeme.joy@paradise.net.nz> to=<graemew@wbc> proto=ESMTP helo=<wbc-server.localdomain>
Aug 13 07:16:35 wbc-server fetchmail[16942]: SMTP error: 504 5.5.2 <graemew@wbc>: Recipient address rejected: need fully-qualified address


I have had no luck configuring fetchmail and virtual mailboxes  .
Can somebody who has a working fetchmailrc that uses virtual domains.
I have had success with real Linux users but not virtual ones.

[lucaspr]

.......
NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 504 5.5.2 <graemew@wbc>: Recipient address rejected: need fully-qualified address; from=<graeme.joy@paradise.net.nz> to=<graemew@wbc> proto=ESMTP helo=<wbc-server.localdomain>
Aug 13 07:16:35 wbc-server fetchmail[16942]: SMTP error: 504 5.5.2 <graemew@wbc>: Recipient address rejected: need fully-qualified address


I have had no luck configuring fetchmail and virtual mailboxes  .
Can somebody who has a working fetchmailrc that uses virtual domains.
I have had success with real Linux users but not virtual ones.

Could you try to change the domain name from wbc into wbc.local? Try a domain name WITH a dot. so wbc.xxxx

Let us know!

[DWAM]

Hi!

I updated eBox (standalone - 32 bits) this morning to core 1.5.11 and access to user corner now works and fetchmail mail retrieval service aswell...

[mparic]

gwoollett,
You need to use the full email address in your fetchmailrc config file. Here's an snip of my working config file that gets the mail and delivers to a virtual account (account only exists in LDAP) with the domain ebox.home.office

poll mail.comcast.net
        proto pop3
        user "mparic"
        pass "password"
        is mparic@home.office
        nokeep
        fetchall
        ssl