Ticket #2095 (closed defect: fixed)
Cannot connect to redis server
| Reported by: | lucero.diego@… | Owned by: | jacalvo@… |
|---|---|---|---|
| Milestone: | 2.0.X | Component: | base |
| Severity: | blocker | Keywords: | |
| Cc: | lucero.diego@… |
Description
When I upgrade to new modules User and Group, Network Configuration and File Sharing. Then restart ebox, the File Sharing Module is stopped and when i start again, show me this: "Cannot connect to redis server"
Trace Cannot connect to redis server at /usr/share/perl5/EBox/Config/Redis.pm line 519.
and the log show me this
EBox::Module::Service::ANON - Error restarting service: Cannot connect to redis server at /usr/share/perl5/EBox/Config/Redis.pm line 519.
How i can fix this problem??.
Diego
Attachments
Change History
comment:1 follow-up: ↓ 2 Changed 3 years ago by jacalvo@…
- Status changed from new to closed
- Resolution set to worksforme
comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 3 years ago by lucero.diego@…
- Status changed from closed to reopened
- Resolution worksforme deleted
Replying to jacalvo@ebox-platform.com:
Make sure you have upgraded to the latest version of the ebox and libebox packages. You can try also to reboot the system after the upgrade if the problem persists.
Since upgrading to the latest version of ebox and also updated packages libebox. ebox restart and the problem persists
comment:3 in reply to: ↑ 2 Changed 3 years ago by Diego Lucero
Resolution: deleted ??
Apologizing but that is what I have to remove the package ebox or libebox. If I make it happen with the information that they are situated on the folder shares.
Thanks
comment:4 Changed 3 years ago by jsoriano@…
- priority changed from normal to highest
- Type changed from feature request to defect
- Milestone set to 2.0
comment:5 Changed 3 years ago by jacalvo@…
- Status changed from reopened to closed
- Resolution set to fixed
Fixed in [18375]
comment:6 Changed 3 years ago by Diego Lucero
jacalvo
Thanks for helping to solve the problem. Make the changes described in Changeset 18 375. Then restart all services and began to work.
Ticket Closed
comment:7 Changed 3 years ago by greg.brumley@…
- Status changed from closed to reopened
- Resolution fixed deleted
I am having this problem on a fresh install 8/24/2010. The solution here seems it was made 12 days ago. I should have the most recent code for this, and it is still a problem. The line number is different (523 v 519).
Trace Cannot connect to redis server at /usr/share/perl5/EBox/Config/Redis.pm line 523.
comment:8 Changed 3 years ago by greg.brumley@…
- Status changed from reopened to new
- Severity changed from normal to blocker
Does anyone read these posts? Is there something that needs to be done to reassign these to someone? I last made a post to this thread on this issue 9 days ago. If Zentyal cannot be used for file and print sharing, then it is pretty much worthless. the concept is great, and the product is good in general, but these little issues that are major blockers will just kill the progress.
comment:9 Changed 3 years ago by lucero.diego@…
- Cc lucero.diego@… added
- Status changed from new to closed
- Resolution set to fixed
Hi Greg. Try to make the following change to the line 522. Then restart the system. Works for me.
496
497 my $response;
498 my @response;
499 my $wantarray = wantarray;
500 my $tries = 5;
501 for my $i (1..$tries) {
502 my $failure;
503 try {
504 if ($wantarray) {
505 @response = $self->{redis}->$command(@args);
506 } else {
507 $response = $self->{redis}->$command(@args);
508 }
509 $failure = 0;
510 } otherwise {
511 # Disconnected, try to reconnect
512 $self->_initRedis;
513 $self->_respawn;
514 $failure = 1;
515 };
516
517 last unless ($failure);
518
519 if ($failure) {
520 if ( $i < $tries) {
521 warn 'Reconnecting to redis server...';
522 } elsif ($failure and $i == 1) {
523 die 'Cannot connect to redis server';
524 }
525 }
526 }
comment:10 Changed 3 years ago by cperez@…
I'm trying to reproduce this issue but i can't, please, can you test again with last 2.0 version and tell me more details?
comment:11 Changed 3 years ago by batonac
- Status changed from closed to reopened
- Resolution fixed deleted
I don't know why this bug says fixed, I have a clean install updated to the latest PPA packages, and the same problem. I followed lucero.diego's advice to get my system working again. Please note and fix this soon or you will have many frustated users who won't be able to use file sharing!
comment:12 Changed 3 years ago by jacalvo@…
We are trying to reproduce it, but we are not able, we have lots of test machines with file sharing running without problems. The patch by lucero.diego only hides the problem connecting to the redis server, but we have to discover the cause.
Of course we always want to fix the problems as soon as possible, but we are already doing as much as we can. Regarding to the many frustated users, take into account that this is a rare problem, there are lots of installations using the file sharing in Zentyal 2.0 without any problem at all.
comment:13 Changed 3 years ago by rutri
I had the same problem, I can reproduce pretty easily. When i installed my printer in CUPS then tried to share that with a user the redis server crashed. Now every time I go to edit the user i get this message "Cannot connect to redis server".
comment:14 Changed 3 years ago by jacalvo@…
- Status changed from reopened to closed
- Resolution set to fixed
Make sure you have upgraded to the latest version of the ebox and libebox packages. You can try also to reboot the system after the upgrade if the problem persists.