powered by Jive Software

Problem uninstalling/reinstalling openfire 3.3.2 (Windows)

All,

I have recently installed openfire and found I need to reconfigure it using another external database (MYSQL). I’ve tried uninstalling openfire, deleting everything in the openfire directory, and reinstalling openfire. When I do this, I am not shown the configuration screen again. I did a search on here and someone mentioned to edit the openfire.xml, changing <setup>false</setup> to true. I do not see this anywhere in the openfire.xml file and when I try to add it, I get errors.

Database setup or configuration error: Please verify your database settings and check the logs/error.log file for detailed error messages.

java.lang.IllegalArgumentException: java.lang.NullPointerException

at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:671)

at org.jivesoftware.openfire.XMPPServer.start(XMPPServer.java:391)

at org.jivesoftware.openfire.XMPPServer.<init>(XMPPServer.java:148)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.openfire.starter.ServerStarter.start(ServerStarter.java:93)

at org.jivesoftware.openfire.starter.ServerStarter.main(ServerStarter.java:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.exe4j.runtime.WinLauncher.main(Unknown Source)

Caused by: java.lang.NullPointerException

at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:660)

… 16 more

Error starting the server. Please check the log files for more information.

Server halted

How can I reconfigure openfire and start from a clean slate?

Hi Josh, welcome to IgniteRealtime community B-).

For re-setup, it has to be:

<setup>false</setup>

If you’re not sure where to place it in openfire.xml, just do it right before at the end of the file. Please copy and paste your openfire.xml here if you’re still having problem.

Here’s the “virgin” openfire.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!--
    This file stores bootstrap properties needed by Openfire.
    Property names must be in the format: "prop.name.is.blah=value"
    That will be stored as:
        <prop>
            <name>
                <is>
                    <blah>value</blah>
                </is>
            </name>
        </prop>     Most properties are stored in the Openfire database. A
     property viewer and editor is included in the admin console.
-->
<!-- root element, all properties must be under this element -->
<jive>
    <adminConsole>
        <!-- Disable either port by setting the value to -1 -->
        <port>9090</port>
        <securePort>9091</securePort>
    </adminConsole>     <admin>
        <!-- Use this section to define users that will have admin privileges. Below,
          you will find two ways to specify which users are admins. Admins will
          have access to the admin console (only local users) and may have also access
          to other functionalities like ad-hoc commands. -->         <!-- By default, only the user with the username "admin" can login
         to the admin console. Alternatively, you can specify a comma-delimitted
         list usernames that should be authorized to login to the admin console
         by setting the <authorizedUsernames> field below. -->
        <!-- <authorizedUsernames></authorizedUsernames> -->         <!-- Comma-delimitted list of bare JIDs. The JIDs may belong to local
         or remote users. -->
        <!-- <authorizedJIDs></authorizedJIDs> -->
    </admin>     <locale>en</locale>     <!-- Network settings. By default, Openfire will bind to all network interfaces.
      Alternatively, you can specify a specific network interfaces that the server
      will listen on. For example, 127.0.0.1. This setting is generally only useful
       on multi-homed servers. -->
    <!--
    <network>
        <interface></interface>
    </network>
    -->
</jive>

You can add the setup tag right before the tag, just like aznidin said.

Maybe you’re editing the wrong file. Make sure it’s in the /conf directory of Openfire instalation that you are using…

Here is my “new” openfire.xml.

<?xml version=“1.0” encoding=“UTF-8”?>

<!–

This file stores bootstrap properties needed by Openfire.

Property names must be in the format: “prop.name.is.blah=value”

That will be stored as:

<prop>

<name>

<is>

<blah>value</blah>

</is>

</name>

</prop>

Most properties are stored in the Openfire database. A

property viewer and editor is included in the admin console.

–>

<!-- root element, all properties must be under this element -->

<jive>

<adminConsole>

<!-- Disable either port by setting the value to -1 -->

<port>9090</port>

<securePort>9091</securePort>

</adminConsole>

<admin>

<!-- Use this section to define users that will have admin privileges. Below,

you will find two ways to specify which users are admins. Admins will

have access to the admin console (only local users) and may have also access

to other functionalities like ad-hoc commands. -->

<!-- By default, only the user with the username “admin” can login

to the admin console. Alternatively, you can specify a comma-delimitted

list usernames that should be authorized to login to the admin console

by setting the <authorizedUsernames> field below. -->

<!-- <authorizedUsernames></authorizedUsernames> -->

<!-- Comma-delimitted list of bare JIDs. The JIDs may belong to local

or remote users. -->

<!-- <authorizedJIDs></authorizedJIDs> -->

</admin>

<setup>true</setup>

<locale>en</locale>

<!-- Network settings. By default, Openfire will bind to all network interfaces.

Alternatively, you can specify a specific network interfaces that the server

will listen on. For example, 127.0.0.1. This setting is generally only useful

on multi-homed servers. -->

<!–

<network>

<interface></interface>

</network>

–>

<setup>false</setup>

</jive>

I’m getting this error now. It says db configuration error…but I haven’t had the option to reconfigure the database…

Database setup or configuration error: Please verify your database settings and check the logs/error.log file for detailed error messages.

java.lang.IllegalArgumentException: java.lang.NullPointerException

at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:671)

at org.jivesoftware.openfire.XMPPServer.start(XMPPServer.java:391)

at org.jivesoftware.openfire.XMPPServer.<init>(XMPPServer.java:148)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.openfire.starter.ServerStarter.start(ServerStarter.java:93)

at org.jivesoftware.openfire.starter.ServerStarter.main(ServerStarter.java:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.exe4j.runtime.WinLauncher.main(Unknown Source)

Caused by: java.lang.NullPointerException

at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:660)

… 16 more

Error starting the server. Please check the log files for more information.

Server halted

You have the setup tag twice. Check right after . write false there, and delete the one you added in the end. It really should show you the admin consoles setup steps again.

Also, make sure you stop Openfire before editing the xml.

Everything works great.

Thanks!

this problem has finish ^^

now i have another problem ^^



hello,
I need your assistance.

I have one linux debian servers.
I had openfire install it ran also, but I wanted to then use it with another domain. as I had changed ran nothing more.

thus I imagined. install it again.

that cannot be done however unfortunately any longer.
I
deleted and also sql the data base the listing. but afterwards it did
not go. I am to always log in. the basic setup does not come any longer.

I already tried described the here away. unfortunately no success: (

still can someone help me?

<?xml version="1.0" encoding="UTF-8"?> 9090 9091

en

false


hallo,

ich brauche eure hilfe.

ich habe einen linux debian server.

ich hatte openfire installiert es lief auch, aber ich wollte es dann mit einer anderen domain benutzen. als ich die geändert hatte lief nichts mehr.

somit dachte ich mir. installiere es neu.

das geht aber leider nicht mehr.

ich habe die sql datenbank gelöscht und auch das verzeichnis. aber danach ging es nicht. ich soll mich immer einloggen. das basic setup kommt nicht mehr.

ich habe auch schon den hier beschriebenen weg versucht. leider kein erfolg

kann mir noch jemand weiterhelfen?

Hi,

did you restart the server? If you did remove the database then Openfire fails to startup fine, so you should see a lot of errors in the log files.

Did you use rpm to the tar.gz file for installation?

Which database are you using?

One usually posts a new thread for every problem … and posting a thread about changing the domain name of Openfire may have been a good idea, re-running the setup does not help.

LG