Ejabberd Error Reading Mnesia
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might ejabberd mnesia location have Meta Discuss the workings and policies of this site About
Error Reading Mnesia Database
Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads
Ejabberd Change Hostname
with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them;
Failed Rpc Connection To The Node Ejabberd@server Nodedown
it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Cannot bring up ejabberd after VPS change made by hosting company up vote 0 down vote favorite 3 My hosting provider WebFusion updated my VPS with failed rpc connection to the node ejabberd localhost nodedown security patches late last night. Since then I cannot start my ejabberd instance. I get the following errors, which seem to indicate that the hostname has changed. =ERROR REPORT==== 2010-11-29 23:01:10 === E(<0.35.0>:ejabberd_config:278) : Error reading Mnesia database spool files: The Mnesia database couldn't read the spool file for the table 'acl'. ejabberd needs read and write access in the directory: /var/lib/ejabberd Maybe the problem is a change in the computer hostname, or a change in the Erlang node name, which is currently: 'ejabberd@lvps109-104-93-116' Check the ejabberd guide for details about changing the computer hostname or Erlang node name. =INFO REPORT==== 2010-11-29 23:01:15 === application: ejabberd exited: {bad_return,{{ejabberd_app,start,[normal,[]]}, {'EXIT',"Error reading Mnesia database"}}} type: temporary Everything has been working a treat for many months and I have made no changes to the VPS configuration, which is based on Ubuntu 8.04 LTS by the way. I have tried everything I could find on Google w.r.t recovering or migrating mnesia files in this type of scenario, but I cannot
Sign in Pricing Blog Support Search GitHub This repository Watch 281 Star 2,671 Fork 844 processone/ejabberd Code Issues 128 Pull requests 20 Projects 1 Wiki Pulse Graphs New issue Change ejabberd host name and ejabberd web admin node name #1023 Closed netknokt opened this Issue Mar 18, 2016 · 7 comments Projects None yet Labels Component:Admin Tools Note:Needs more info Milestone No milestone Assignees badlop 3 participants netknokt commented Mar 18, 2016 What version of ejabberd are you using? 2.1.11-1ubuntu2.1 What operating system (version) are you using? Ubuntu 14.04 How did you install ejabberd (source, package, distribution)? distribution What did not work as http://serverfault.com/questions/207506/cannot-bring-up-ejabberd-after-vps-change-made-by-hosting-company expected? Are there error messages in the log? What was the unexpected behavior? What was the expected result? I'm trying to change the hostname of the host and following the instructions here (https://docs.ejabberd.im/admin/guide/managing/#change-computer-hostname) but it doesn't work at all. I get to Step 4&5 which looks like this: root@m:~# mv /var/lib/ejabberd/*.* /var/lib/ejabberd/oldfiles/ root@m:~# ejabberdctl start The node ejabberd@m is started with status: started ejabberd is not running in that node https://github.com/processone/ejabberd/issues/1023 Check for error messages: ejabberd.log or other files in that directory. Error in ejabberd ctl process: 'error' badarg I've tried lots of variations, to no avail. If the node won't run ejabberd, I can't get anywhere. And removing all the files from /var/lib/ejabberd really seems to not help at all badlop was assigned by mremond Mar 18, 2016 ProcessOne - XMPP, Erlang, jabber member badlop commented Mar 19, 2016 Error in ejabberd ctl process: 'error' badarg Is the error message longer? I mean, does it provide anything else other than just "error badarg"? And removing all the files from /var/lib/ejabberd really seems to not help at all I assume that dir is where ejabberd creates the mnesia spool files when starts the first time in your system: caps_features.DAT irc_custom.DCD last_activity.DCD LATEST.LOG motd.DCD ... Please note that maybe the Ubuntu package for ejabberd uses another path for those files. netknokt commented Mar 20, 2016 I assume that dir is where ejabberd creates the mnesia spool files when starts the first time in your system: caps_features.DAT irc_custom.DCD last_activity.DCD LATEST.LOG motd.DCD ... You are correct. Old host name of machine: "mail" New host name of machine "m" Thanks. ****** Log file ******* =INFO REPORT==== 2016-03-19 01:42:51 === I(<0.41.0>:ejabberd_app:89) : ejabberd 2.1.11
through our pages. Any action in this website implies consent for installation and usage. For more information see our cookies policy. close https://forum.zentyal.org/index.php?topic=13995.0 Exchange email on Linux Zentyal Server Commercial Edition Development Edition Code Tracker http://stackoverflow.com/questions/4350311/how-to-stop-ejabberd-from-using-mnesia I need help Documentation Forum Training Stay tuned Community News Zentyal Labs About us About Zentyal Careers Contact us Home Login Register 1 Hour 1 Day 1 Week 1 Month Forever Please login or register. Zentyal Forum, Exchange email on Linux » Zentyal Server » error reading Installation and Upgrades » Can't start ejabberd / Jabber « previous next » Print Pages: [1] Author Topic: Can't start ejabberd / Jabber (Read 1324 times) mokkin Zen Apprentice Posts: 6 Karma: +0/-0 Can't start ejabberd / Jabber « on: February 12, 2013, 09:36:39 pm » Hello everybody,my Zentyal 3.0 machine runs fine, but I cannot start error reading mnesia the ejabberd service. The start button in th webinterface remains always green. All modules are up to date.If you try to start it by command line it doesn't work too.ejabberd.log says:Code: [Select]root@server:/var/log/ejabberd# cat ejabberd.log
=INFO REPORT==== 2012-11-08 23:25:53 ===
I(<0.471.0>:ejabberd_listener:166) : Reusing listening port for 5222
=INFO REPORT==== 2012-11-08 23:25:53 ===
I(<0.472.0>:ejabberd_listener:166) : Reusing listening port for 5269
=INFO REPORT==== 2012-11-08 23:25:53 ===
I(<0.473.0>:ejabberd_listener:166) : Reusing listening port for 5280
=INFO REPORT==== 2012-11-08 23:25:53 ===
I(<0.37.0>:ejabberd_app:72) : ejabberd 2.1.10 is started in the node ejabberd@rv1087
=INFO REPORT==== 2012-11-08 23:28:52 ===
I(<0.37.0>:ejabberd_app:89) : ejabberd 2.1.10 is stopped in the node ejabberd@rv1087
=INFO REPORT==== 2012-11-08 23:28:54 ===
I(<0.307.0>:eldap:983) : LDAP connection on 127.0.0.1:390
=INFO REPORT==== 2012-11-08 23:28:54 ===
I(<0.317.0>:eldap:983) : LDAP connection on 127.0.0.1:390
=ERROR REPORT==== 2012-11-08 23:28:54 ===
E(<0.368.0>:eldap_utils:166) : failed to parse LDAP filter:
** Filter: []
** Reason: {error,["syntax error before: ",[]]}
=INFO REPORT==== 2012-11-08 23:28:54 ===
I(<0.373.0>:eldap:983) : LDAP connection on 127.0.0.1:390
=INFO REPORT==== 2012-11-08 23:28:54 ===
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to stop ejabberd from using mnesia [closed] up vote 2 down vote favorite 1 I'm trying to establish a procedure for restoring my database from a crashed server to a new server. My server is running Ejabberd as an XMPP server, and I configured it to use postgresql instead of mnesia - or so I thought. My procedure goes something like "dump the contents of the original DB, run the new server, restore the contents of the DBs using psql, then run the system". However, when I try running Ejabberd again I get a crash: =CRASH REPORT==== 3-Dec-2010::22:05:00 === crasher: pid: <0.36.0> registered_name: [] exception exit: {bad_return,{{ejabberd_app,start,[normal,[]]}, {'EXIT',"Error reading Mnesia database"}}} in function application_master:init/4 Here I was thinking that my system is running on PostgreSQL, while it seems I was still using Mnesia. I have several questions: How can I make sure mnesia is not being used? How can I divert all the ejabberd activities to PGSQL? This is the modules part in my ejabberd.cfg file: {modules, [ {mod_adhoc, []}, {mod_announce, [{access, announce}]}, % requires mod_adhoc {mod_caps, []}, {mod_configure,[]}, % requires mod_adhoc {mod_ctlextra, []}, {mod_disco, []}, {mod_irc, []}, {mod_last_odbc, []}, {mod_muc, [ {access, muc}, {access_create, muc}, {access_persistent, muc}, {access_admin, mu