Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1690 views

Multiple Kanaka Engines

I know I can export the runtime config for the engine. Is there a way to import it to another machine running the kanaka engine? I'm wanting to get some redundancy set up in a round-robin fashion for my mac users.
Labels (1)
0 Likes
13 Replies
Absent Member.
Absent Member.

isutton,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
Absent Member.
Absent Member.

I believe the runtime configuration is more for troubleshooting than anything else. I don't believe there is a way to import that into another server; however, configuration is simple and straightforward, so it shouldn't take long to set it up.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 4/15/2013 1:56 PM, joharmon wrote:
>
> I believe the runtime configuration is more for troubleshooting than
> anything else. I don't believe there is a way to import that into
> another server; however, configuration is simple and straightforward, so
> it shouldn't take long to set it up.


Yes you can, it is in the docs under migrating.

However, they should but do not call out that if you start the second
one up, it will overwrite the KAnaka proxy password, so make sure to
change the user used as the proxy. Oopsey.

I am not sure how to regenerate the password for that account, so if
anyone does, let me know!


0 Likes
Absent Member.
Absent Member.

geoffc;2275377 wrote:
On 4/15/2013 1:56 PM, joharmon wrote:
>
> I believe the runtime configuration is more for troubleshooting than
> anything else. I don't believe there is a way to import that into
> another server; however, configuration is simple and straightforward, so
> it shouldn't take long to set it up.


Yes you can, it is in the docs under migrating.

However, they should but do not call out that if you start the second
one up, it will overwrite the KAnaka proxy password, so make sure to
change the user used as the proxy. Oopsey.

I am not sure how to regenerate the password for that account, so if
anyone does, let me know!


Proxy user password is stored on the object itself and in the casa credentials as seen under CASAcli -l

You can reset the password on the eDir object as you do with any other user object. You then have to change the password stored for the user in the casa credentials.
See CASAcli -h for help. The bottom reports the following:
KEYVALUE=<cn=admin,o=novell> CASAcli -s -n <MyCredential> -k CN
KEYVALUE=<password> CASAcli -s -n <MyCredential> -k Password

To set the password on a cred, you can do something like:
KEYVALUE=mysecret CASAcli -s -n afp-casa -k Password

afp-casa as reported under CASAcli -l. Each service may have its own casa store.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 8/1/2013 3:06 PM, joharmon wrote:
>
> geoffc;2275377 Wrote:
>> On 4/15/2013 1:56 PM, joharmon wrote:
>>>
>>> I believe the runtime configuration is more for troubleshooting than
>>> anything else. I don't believe there is a way to import that into
>>> another server; however, configuration is simple and straightforward,

>> so
>>> it shouldn't take long to set it up.

>>
>> Yes you can, it is in the docs under migrating.
>>
>> However, they should but do not call out that if you start the second
>> one up, it will overwrite the KAnaka proxy password, so make sure to
>> change the user used as the proxy. Oopsey.
>>
>> I am not sure how to regenerate the password for that account, so if
>> anyone does, let me know!

>
> Proxy user password is stored on the object itself and in the casa
> credentials as seen under CASAcli -l
>
> You can reset the password on the eDir object as you do with any other
> user object. You then have to change the password stored for the user
> in the casa credentials.
> See CASAcli -h for help. The bottom reports the following:
> KEYVALUE=<cn=admin,o=novell> CASAcli -s -n <MyCredential> -k CN
> KEYVALUE=<password> CASAcli -s -n <MyCredential> -k Password
>
> To set the password on a cred, you can do something like:
> KEYVALUE=mysecret CASAcli -s -n afp-casa -k Password
>
> afp-casa as reported under CASAcli -l. Each service may have its own
> casa store.


Is that the KanakaProxy.acme account that is specified in the salt.dat
file? Or are you referring to the AFP/CIFS/Common proxy passwords?

I feel the latter.

My issue is not the AFP services' password, but rather the KanakaProxy
account password.

I see this in trace on the original server:
01 2013-08-01 14:29:29 -14400 3 0001 2548 2080 ML: Failed to
authenticate as the Proxy Account, Result = 185.


0 Likes
Absent Member.
Absent Member.

You are right, the latter.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 8/1/2013 3:26 PM, joharmon wrote:
>
> You are right, the latter.


But my issue is the former. Any thoughts on that?

How can I make Kanaka reset the KanakaProxy account that it maintains?

The Salt.dat file stores a <salt> and a <Account> node.

How do I change Server1 to use KanakaProxy.acme, and Server2 to use
KanakaProxy2.acme, after the fact.

I have a lot of config info I do not wish to reenter to throw away the
config to try and get the Wizard to run again?

I followed the mIgration instruction except for this one detail.


0 Likes
Absent Member.
Absent Member.

stop the kanaka engine with rcnovell-kanakaengined stop then run rcnovell-kanakaengined proxy-reset
0 Likes
Absent Member.
Absent Member.

also, you can get the setup wizard to run again by renaming or moving your license file and restarting the engine - that might be helpful if you want to change the proxy user object name
0 Likes
Absent Member.
Absent Member.

ignore that last comment... I don't believe Novell's version has a license.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 8/1/2013 4:16 PM, joharmon wrote:
>
> ignore that last comment... I don't believe Novell's version has a
> license.


Ya no license file.

If I edit the salt.dat, change the <Account> node to KanakaProxy2.acme
and do the proxy-reset will it create the new account and all that jazz?

Also, what is the Winders equivalent to the OES/Linux command you
suggest? (Server1 is Winders, Server2 is OES 11 SP1).



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.