Hi everyone,
I've just installed RC 0.9.2 via the bitnami RoundCube installer on a Mac OS X Server 10.8.4. Everything appeared to install correctly.
When I'm presented with the RC login at http://localhost/roundcube, I'm unable to log in to any of my email accounts hosted on the server. I keep getting login failed on the login screen.
I'm a complete RC newbie, and I'm unsure where to go from here. Can someone help?
John
Hi all,
I have an old 0.3.1 instance running, with a fully customized skin.
I plan to upgrade to the latest stable RC.
Is there a reasonable chance to migrate the custom skin to the new one
or it has to be redone from scratch?
Thanks
Bgs
>>>> Can anything be done to speed up Roundcube on a Celeron 700 with 512MB
>>>> RAM (maxed out) running Gentoo Linux? We're using the Chrome browser
>>>> and the CPU is 95% idle when no one is logged into X. I'm getting
>>>> reports of 30+ seconds to open an email.
>>>
>>> no - you should be happy that it runs at all on
>>> hardware outperfored by years old smartphones
>>
>> What are the Roundcube recommended minimum specs?
>
> i don't know
>
> but a 700 MHz/512 MB machine is far below the minimum
> specs of any modern operating system at all - hence
> you even get not a Fedora/Ubuntu installer started
> full featured on it
I don't mean to call you foolish but I think that's a foolish
statement. I use Gentoo which is a modern OS and the system in
question surpasses the published hardware requirements for Gentoo on
x86:
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=2#doc_ch…
- Grant
>>> but a 700 MHz/512 MB machine is far below the minimum
>>> specs of any modern operating system at all - hence
>>> you even get not a Fedora/Ubuntu installer started
>>> full featured on it
>>
>> I don't mean to call you foolish but I think that's a foolish
>> statement. I use Gentoo which is a modern OS and the system in
>> question surpasses the published hardware requirements for Gentoo on
>> x86:
>>
>> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=2#doc_ch…
>
> but not for Fedora and other distributions - period
> for the live-CD the *minimum* is 512 MB
>
> well, you can't expect a fast system with *minimum* requirements
> it only says "it works somehow"
>
> and yes i have servers with 512 MB RAM assigned but they do not
> run a GUI and this ones have no load
I'm going to fix the problem (probably by simply switching browsers)
and the system is going to run perfectly well on its current OS.
- Grant
Hi all,
I encountered the same proble with a FRESH roundcube installation (0.9.2),
with a clean MySQL database.
How can I debug this?
Thank you!
>----Messaggio originale----
>Da: absolutely_free(a)libero.it
>Data: 11/07/2013 16.38
>A: <users(a)lists.roundcube.net>
>Ogg: [RCU] Problem showing HTML message
>
>Hi,
>I'm using Roundcube 0.9.2 on Debian 6.0.7.
>Some users complain about problem reading HTML messages.
>I think this is related to recent upgrade (from RCB 0.8.5); anyway I'm sure
I
>followed correct steps to upgrade webmail.
>Users see message body totally white, and if you try to see the original
>header, all part of the body is missing.
>I've tried to copy a html message to another RC webmail (same version:
0.9.2)
>and I can succesfully it correctly.
>
>I've no error on apache/error.log
>Can you help me troubleshooting this?
>
>Thank you
>_______________________________________________
>Roundcube Users mailing list
>users(a)lists.roundcube.net
>http://lists.roundcube.net/mailman/listinfo/users
>
We are currently running a pilot Roundcube service and are expecting to go
live a a couple of weeks time. Something that my users have picked up on
is that idle sessions appear to time out in unpredictable ways despite the
keep_alive requests fired off by the Web browser.
A bit of digging over the weekend revealed a potential race condition in
program/lib/Roundcube/rcube_session.php : mc_write(). (Roundcube 0.9.2).
I'm happy to write the following up as a ticket on trac.roundcube.net. I
wanted to make sure my analysis and proposed solution was correct first.
Given the 10 minute (600 second) default session_lifetime, keep_alive
requests are fired off every 300 seconds. However these may not arrive
immediately, particularly if the Web browser, network or server is busy.
Sessions stored in memcached expire after precisely 600 seconds unless
they are refreshed.
mc_write() only refreshes session entries if the following is true:
($newvars !== $oldvars || $ts - $this->changed > $this->lifetime / 2)
Most of the time with a idle login session:
($this->lifetime / 2) will be 300
($ts - $this->changed) will be a tiny fraction more than 300.
However if I add some logging it becomes clear that ($ts - $this->changed)
is occasionally less than 300. I imagine this happens when the previous
keep_alive was stuck in transit for a fraction of a second. It is an
asynchronous request and the timer for the next keep_alive doesn't wait.
The mc_write() refresh on the session data is skipped when this happens.
The following keep_alive is scheduled to arrive precisely the same second
that the session is due to expire in memcached. If you are unlucky the
keep_alive arrives just after the session has been expired, which leads a
"Session is invalid or has expired" error page.
This is using memcached for session storage: the problem appears to go
away if I switch to using a database backend. I believe that this is
because session entries stored in memcached expire after precisely 600
seconds. With a database backend sessions are expired by PHP garbage
collection later on. This will add a few seconds delay, at least on a
inactive system.
The attached patch appears to fix the problem, using two separate
approaches:
1) A lower threshold for deciding when to refresh the session entry. (I am
tempted to remove the guard condition altogether and always update.
There isn't any I/O cost associated with a memcached back end).
2) A slightly longer expiry time for entries stored in memcached.
However I may be missing some subtlety about the refresh process.
--
David Carter Email: David.Carter(a)ucs.cam.ac.uk
University Computing Service, Phone: (01223) 334502
New Museums Site, Pembroke Street, Fax: (01223) 334679
Cambridge UK. CB2 3QH.
--- program/lib/Roundcube/rcube_session.php-DIST 2013-07-21 12:11:49.000000000 +0100
+++ program/lib/Roundcube/rcube_session.php 2013-07-22 10:00:40.000000000 +0100
@@ -310,9 +310,9 @@
$newvars = $oldvars !== null ? $this->_fixvars($vars, $oldvars) : $vars;
- if ($newvars !== $oldvars || $ts - $this->changed > $this->lifetime / 2) {
+ if ($newvars !== $oldvars || $ts - $this->changed > $this->lifetime / 3) { // DPC
return $this->memcache->set($key, serialize(array('changed' => time(), 'ip' => $this->ip, 'vars' => $newvars)),
- MEMCACHE_COMPRESSED, $this->lifetime);
+ MEMCACHE_COMPRESSED, $this->lifetime + 60); // DPC
}
return true;
>> Can anything be done to speed up Roundcube on a Celeron 700 with 512MB
>> RAM (maxed out) running Gentoo Linux? We're using the Chrome browser
>> and the CPU is 95% idle when no one is logged into X. I'm getting
>> reports of 30+ seconds to open an email.
>
> no - you should be happy that it runs at all on
> hardware outperfored by years old smartphones
What are the Roundcube recommended minimum specs?
- Grant
Hi Fellow Roundcube users
can anyone help with an idiots guide to setting up round cube on my Mac Desktop - I get as far as downloading round cubemail 0.9.2 and then cannot find the install on the download - any help appreciated
Regards
FCH