Building Elastix 4 via RPM Repo
-
@dom said:
@3Mu36 said:
ping fqdn
Weird
ping pbx77.cloudapp.net
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.063 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.098 mswhen I install a standard lamp stack on azure its fine its just this Elastix installation thats a problem
Try another Elastix install on Azure. Right now, Azure is partially down (we have several VMs not responding, the console is regionally down and some Exchange customers are having issues.) But once Azure recovers, see if a fresh build has the same issues.
-
Does anybody knows why does the elastix installation changes the root password of the machine? I'm trying to install Elastix 4 on Amazon Web Services.
Thanks
Thiago Lima -
@thiagolima said:
Does anybody knows why does the elastix installation changes the root password of the machine? I'm trying to install Elastix 4 on Amazon Web Services.
I have not experienced this. But we use keys so might not notice. Are you sure that it is doing so and not something else doing it?
Just set up an SSH Key for root before installing and this will not be a problem.
-
@scottalanmiller Yes, I always use the keys and never the passwords. And that's the root of all my issues. After the install, when I try to run commands as sudo (or try 'sudo su' or even 'su -'), it is asked for a root password that I've never set. Thus, I'm locked outside my own box.
I still don't know why it is happening, but I could manage to get this working by doing the following workaround (not a very elegant solution, but at least worked):
- I've opened two ssh sessions and became root with 'su -' on one of them;
- On the other one, I've installed the elastix with your script but I've commented the 'reboot' command;
- Before rebooting the system, at the session that I'm root, I've manually changed the root and centos passwords for ones of my acknowledge;
- Rebooted the system and everythning runs like clockwork! (hey mom, look! I'm smart! =P).
Again, it is nothing that I'm really proud of. But at least I'm still logging with keys and not using passwords and I've set some pretty secure passwords, so I can't see any danger here.
And this is a problem affecting just the CentOS provided by CentOS itself for Amazon Web Services. I have Elastix MT running on Digital Ocean and I don't really think it would happen there for Elastix 4.
So here's my testimonial. If you can think on a better sollution, I'd really happy to hear!
If I think on anything better than this, I'm posting here. Your assistance with this installing guide in a form of a script was very very helpful and I'm really thankful already. -
@3Mu36 +1 on this solution. Not that I'm planning to leave like that but at least it is a good test if you're facing error 500.
-
@thiagolima said:
@scottalanmiller Yes, I always use the keys and never the passwords. And that's the root of all my issues. After the install, when I try to run commands as sudo (or try 'sudo su' or even 'su -'), it is asked for a root password that I've never set. Thus, I'm locked outside my own box.
This is not the same as what you had asked (it is not changing any passwords) and is a well known issue with Elastix: it has always changed the sudoers file.
We talked about this issue somewhere above. Sadly, this is simply how Elastix works and you've always needed to deal with this when working with Elastix. There are a few decent choices but you need keys for root and this won't be a problem. You mentioned that you had the root password change, but that's not what changed.
Just set a root key and you are fine. It's trying to use the non-standard sudoers mechanism that Elastix does not intend you to use that causes an issue. Sudoers is awesome and we always use it so I totally feel your pain, but it's just something you have to know with Elastix.
Somewhere in the thread I showed to someone who was facing this, as we all do, that you can make your sudoers file something like /etc/sudoers.master and run a cronjob to copy that file to the /etc/sudoers file every fifteen minutes or whatever. Cheesy but effective. That's all that is needed. No passwords or keys are changed by Elastix.
-
@thiagolima said:
And this is a problem affecting just the CentOS provided by CentOS itself for Amazon Web Services. I have Elastix MT running on Digital Ocean and I don't really think it would happen there for Elastix 4.
Unless something is modifying the sudoers behaviour, it will happen everywhere. It is one of the RPMs for Elastix overwrites that file whenever it updates. So be prepared, it happens over and over. Digital Ocean you probably don't notice because as a standard install step they set up root, not user, keys without sudoers. So the issue is bypassed by Digital Ocean doing what I said to do on their own
-
I installed Elastix using your script, hasn't worked out for me. Any tips on how to uninstall?
-
@yonniz said in Building Elastix 4 via RPM Repo:
I installed Elastix using your script, hasn't worked out for me. Any tips on how to uninstall?
You would never uninstall Elastix, you would just create a new VM in its place.
-
What is your end goal now; what are you trying to install?
-
@yonniz how is your project going?
-
I added a disclaimer and warning to the original post to let people know that FreePBX is the better way to go at this point.
-
also forked out the most recent topic so that we could address it on its own.
-
@scottalanmiller said in Building Elastix 4 via RPM Repo:
ested as working for
Hello
Where can i get your script ? please -
@professionel said in Building Elastix 4 via RPM Repo:
@scottalanmiller said in Building Elastix 4 via RPM Repo:
ested as working for
Hello
Where can i get your script ? pleaseIt's the very first post, just use the up arrows to navigate to the top, scroll up manually (it is a long way) or alter the URL to remove the number at the end after the last / (probably something like 177)
-
@professionel welcome to the community, by the way.
While you are asking, though, I should point out (and it says this in the top post) that Elastix 4 is not stable and not well supported. We all highly recommend using FreePBX instead, today, in 99% of cases. I would definitely look at that first, before going down the Elastix 4 path.
-
Another update, Elastix is gone now, the product at least. So it should be out of the question to be attempting to do this at this point.
-
@scottalanmiller said in Building Elastix 4 via RPM Repo:
Another update, Elastix is gone now, the product at least. So it should be out of the question to be attempting to do this at this point.
I was wondering if the last nail was ever going to be pounded.
-
@Dashrender said in Building Elastix 4 via RPM Repo:
@scottalanmiller said in Building Elastix 4 via RPM Repo:
Another update, Elastix is gone now, the product at least. So it should be out of the question to be attempting to do this at this point.
I was wondering if the last nail was ever going to be pounded.
Here or by 3CX?
-
@scottalanmiller said in Building Elastix 4 via RPM Repo:
@Dashrender said in Building Elastix 4 via RPM Repo:
@scottalanmiller said in Building Elastix 4 via RPM Repo:
Another update, Elastix is gone now, the product at least. So it should be out of the question to be attempting to do this at this point.
I was wondering if the last nail was ever going to be pounded.
Here or by 3CX?
either/both.
