Jump to content

Ahbot enabling?


Recommended Posts

Posted

Hello :)

I seem not to be able to kickstart AHbot.

I did duplicate the default ahbot.conf.dist file into a valid ahbot.conf, with seller and buyer enabled of course.

Then restarted mangosd.

Log still says "ahbot not enabled".

What am I doing wrong? :(

Thanks for continued help 

ciao

U

Posted
1 minute ago, antz said:

sorry I misread that, you say that you have enabled both.... in the conf ?

yes. In the etc directory now I have an "ahbot.conf" file, where I have 

AuctionHouseBot.Seller.Enabled = 1

and

AuctionHouseBot.Buyer.Enabled = 1

 

Btw, I also left 

AuctionHouseBot.CharacterName  = ""

 

as the comments, above, say

#    Default "" (No owner)

 

Ciao

U

 

Posted

world-server.log tells me 

2017-05-21 18:25:59 Initialize AuctionHouseBot...
2017-05-21 18:25:59 AHBOT is Disabled. Unable to open configuration file ../etc/ahbot.conf. 
 

But the conf file is there, and with the right privileges...

 

Posted

Without me changing anything else, ahbot started working. Meaning, mangosd now "can" read ahbot.conf.

I must conclude that, previously, the conf file appeared busy by whatever other process.

Anyhow, solved (by itself) now :)

Posted

I got the problem again.

Yesterday I rebuilt the whole Zero thing to include playerbots.

After the rebuild, again I have

AHBOT is Disabled. Unable to open configuration file ../etc/ahbot.conf. 

in the world-server.log file

Needless to say, ahbot.conf staid there since before, nothing changed, no permissions changed etc etc

There seems to be no other process tampering with it.

Where's the catch??

 

Thanks

U

Posted

I think I found where the issue stays. Didn't solve it yet though.

 

After rebuilding, 

if I launch mangosd as a normal binary (./mangosd), ahbot.conf is properly read-in and all works

If I launch mangosd as a service (as I configured it earlier as per wiki instructions) ahbot.conf is NOT read-in !

 

 

Any clue how to fix this?

 

Thanks ciao

U

 

Posted

Sounds logical.

Yet, I am positive this *did* work, without -c option for ahbot.conf, as a service at least once before. Odd i'ni?

I'll try and add the -c opt and feedback here

 

ciao

U

  • 11 months later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use