unable to utilize xl toolstack with cloudmin

Submitted by cesurasean on Fri, 09/02/2016 - 23:29

Error im getting is this;

Detailed status error Could not fetch Xen instances : WARING: Can't find toolstack xm, fallback to default! ERROR: A different toolstack (xl) have been selected!

1.) What exactly is a 'waring'? Spelling?

2.) Debian 8 doesn't seem to support xm toolstack anymore, but I COULD be wrong! Cloudmin doesn't seem to support xl yet.

I'm technically stuck trying to utilize cloudmin, and xen. I almost want a refund for my purchase of cloudmin, as it seems to be very buggy with xen and debian ( perhaps it's using all together ). I'd like to get my license extended for the issues, so we can work through them and make cloud/debian/xen work together on Jessie.

-Sean

Status: 
Active

Comments

Submitted by JamieCameron on Sat, 09/03/2016 - 01:00

Cloudmin's latest release does support both the xm and xl toolstacks.

But if the xm command is installed but not working, you might get this error. Try renaming the xm command to something like xm.disabled

Submitted by cesurasean on Sat, 09/03/2016 - 01:04

they both seem to be installed, and working, but it seems to be chosing xl and not working when i specify xm inside the configs. seems cloudmin only wants to read xl configs....

please advise.

Submitted by cesurasean on Sat, 09/03/2016 - 01:06

is that the only way to disable xm or xl?

Submitted by JamieCameron on Sat, 09/03/2016 - 12:37

The next Cloudmin release will properly detect the case where the xm command is installed, but doesn't work properly.

Submitted by cesurasean on Sat, 09/03/2016 - 15:50

well, it seems the issue is BOTH are installed at the same time, I believe.....

xl, and xm both work on the command line, but the cloudmin complains about using the opposite one.

Submitted by cesurasean on Sat, 09/03/2016 - 15:50

cloud should detect which is installed, and which one should be used, even if both are installed.

Submitted by JamieCameron on Sat, 09/03/2016 - 16:46

Yes, the next release will detect the correct version.

Submitted by cesurasean on Sat, 09/03/2016 - 17:21

Ok, so is there anyway to extend my registration since I was unable to successfully use your software due to errors, etc? 1 month at least? Enough time for you to fix, and then me having running correctly? My username is cesurasean for registration.

Submitted by JamieCameron on Sat, 09/03/2016 - 19:20

Sure, but did you first try running mv /usr/bin/xm /usr/bin/xm.disabled to force use of the new xl command?

Submitted by cesurasean on Sat, 09/03/2016 - 21:59

root@vm:/home/sbrady# mv /usr/bin/xm /usr/bin/xm.disabled mv: cannot stat ‘/usr/bin/xm’: No such file or directory

I was wrong, perhaps it's not xm installed. just xl is what i have, i believe.

Submitted by cesurasean on Sat, 09/03/2016 - 21:59

so, the issue is cloudmin is trying to use xm, when only xl is installed. how do i tell cloudmin i only have xl? and to use xl?

Submitted by cesurasean on Sat, 09/03/2016 - 22:01

perhaps you can give user the choice between which toolkit they are using?

Submitted by cesurasean on Sat, 09/03/2016 - 22:02

i believe debian has switched from xm to xl in jessie 8.0

Submitted by cesurasean on Sat, 09/03/2016 - 22:04

same problem as https://www.virtualmin.com/node/40722

so needs to be reopened. cloudmin is not detecting xl is the only thing installed. it seems to think xm is installed, for some reason.

you could check the xen config file, to determine which is being used?

Submitted by cesurasean on Sat, 09/03/2016 - 22:06

/etc/default/xen

shows which toolstack is used. cloudmin should read this command in the file and figure out which is being used, and also WHICH are installed also, to double check.

im not sure what your current code DOES, but it obviously sucks on jessie for whatever reasons.

please extend out my membership with you, and ill be glad to point out and follow along with errors i find in cloudmin. it has been several years since we've spoke.

-Sean

Submitted by cesurasean on Sat, 09/03/2016 - 22:07

you claimed to have already fixed this issue, in the bug tracker. is there a reason it's not working for me then???!

Submitted by JamieCameron on Sun, 09/04/2016 - 19:39

"Fixed" means that the fix has been coded, but we haven't released a new version of Cloudmin that includes the fix yet.

Submitted by cesurasean on Mon, 09/05/2016 - 14:20

Do you have an estimated date on release of the fix?

Submitted by andreychek on Mon, 09/05/2016 - 14:57

Jamie said that a new Cloudmin release would be coming out soon. This is a holiday weekend in the US, so it won't be today -- but I suspect it'll be this week.

Submitted by JamieCameron on Mon, 09/05/2016 - 18:13

It should be out today or tomorrow - I'm running final tests on the new version now.