No Provision After Accepting Order

[astroroxy]

After having the option to manually approve all orders, and I approve it via the billing widget, it does not get provisioned.

[domaingood]

Did you added cron ?

[astroroxy]

Yep,

 

Works fine if Require Manual Review and Approval of All Orders is not selected

[Paul]

When you approved the order, did the service become a "Pending" service? Has the invoice been paid? If the invoice is paid, and the service is a pending service, it should be activated by cron. If it isn't check the module log under Tools > Logs > Module.

[Michael]

Well it might be something server side. Because when you have manually provision. You have to accept it. It then is pending and when the cron runs it makes it active unless there's a unpaid invoice for it.

[astroroxy]

It is under pending, but I paid the invoice manually after accepting it.

Also impossible for me to go through the module logs. It is spammed from solusvm

[Michael]

It is under pending, but I paid the invoice manually after accepting it.

Also impossible for me to go through the module logs. It is spammed from solusvm

 

It should run 5 minutes after you paid...

[astroroxy]

I know, that's why I am here 

The cron says its doing its job in the logs too.

[Paul]

I know, that's why I am here 

The cron says its doing its job in the logs too.

 

Does the cron log show that the service was successfully created via the API? If so, was it? Something doesn't sound right.

[astroroxy]

Unfortunately the logs cut out already by one day.

It does say Attempting plugin cron for order accept_paid_orders. Finished plugin cron for order accept_paid_orders. every five min.

[Michael]

You need the modules logs mate.

[astroroxy]

Finally found the issue. Just me being stupid.

The problem is that the node was in the wrong node group for solusvm.

Solusvm showed the error in the log, but for some reason I could not find it in blesta. It turns out I did not scroll far down enough. Now I understand why it was spamming solusvm with requests.

It would be nice if we could get an email if a service fails to provision, and provide the error message.

[Michael]

Finally found the issue. Just me being stupid.

The problem is that the node was in the wrong node group for solusvm.

Solusvm showed the error in the log, but for some reason I could not find it in blesta. It turns out I did not scroll far down enough. Now I understand why it was spamming solusvm with requests.

It would be nice if we could get an email if a service fails to provision, and provide the error message.

 

You can My info > Notices > Creation error.

 

If it's not there Settings > System > Staff > Staff groups > edit Admin > tick boxes.

 

Eg:

Hi Michael,

There was an error provisioning the following service:

Service Name
--
Client ID
Client Name
Client Email Address

Manage Service

The pending service may need to be modified so that it can be provisioned automatically or it may need to be provisioned manually.

Error: ErrorCode:-9001|Message:General System Error. Please contact your service provider.

[Paul]

We have plans to rate limit provision requests, such that if it  fails so many times it stops attempting to provision the service. This would be a good time to add an email alert, or an alert in the admin area. CORE-901