deed02392's questions

When I try to connect to SSL enabled proftpd as installed on Freenas 8.3.0, I see my client feedback output saying that AUTH TLS is working, the connection goes encrypted (as confirmed by Wireshark) and everything goes as far as:

[2] MLSD
[2] 150 Opening ASCII mode data connection for MLSD

After a while of nothing happening I get:

[2] 425 Unable to build data connection: Operation not permitted

The exact same configuration, less the SSL related directives (unchecking 'Enable SSL' in the FreeNAS GUI), works perfectly.

I have a cheap but powerful dedicated server I am leasing with OVH, because they were recently having a promotion. I would like to try and manage all this power by playing with VMs using ESXi.

However I am only provided with a single NIC.

I had thought this would be easy to get around since, at home I have a single NIC which is my broadband modem, and yet a simple NAT gateway device happily provides internet access to all my devices.

I am struggling to implement this on ESXi, though. Can anyone advise on how I could go about having ESXi and multiple VMs working with just one NIC?

Here's my current setup:

I believe all I need is to be able to configure NAT from the NIC to all the VMs etc.. How would I set up and administer this kind of infrastructure?

I set up a FreeNAS box a while ago and against better judgement, used an uppercase character when creating my username. This has led to a directory called George.

Now, when I later read that uppercase characters were highly discouraged, especially in the use of Samba (which I'm using), I decided I'd like to try and repair this.

What steps should I take to rename a user account from mixed uppercase to all lowercase, bearing in mind that data already exists for this user?

I am planning to deploy an infrastructure of 11 nodes using Opscode Chef, providing for a high availability web application. I would like to spread the nodes across datacentres for availability, for which I'm thinking rrDNS which resolves to one of two load-balancers, each in a separate datacentre with its own clustered nodes (providing the application with nginx, memcached and Sphinx). A third DC will be used for a MySQL master/slave arrangement, as I have read replication does not perform well over WAN. This solution enables no single point of failure.

My question pertains to how these nodes should connect to one another? All the information transferred by these services is generally expected to go over short LAN connections, hence no in-built security is provided, meaning I will need to provide this on the links themselves.

I was thinking of doing this with SOCKS tunnelling or VPN. The latter would double as increasing security for the nodes themselves, as then they do not need to expose several services on their Internet interface, instead just exposing say an instance of OpenVPN.

What are the thoughts on solutions for providing links between nodes in this sort of infrastructure?

I'm having an issue with pma whereby after logging in (as root or the database owner), and trying to switch to a certain database, I am automatically logged out. I cannot do any actions on the database and in the page that loads immediately before I'm logged out I note that I can't see any tables in the database. The database is accessible by the cli mysql program and all records are still present.

To clarify:

Literally login works fine, I can browse ALL databases except the one of my projects. Trying to use that database causes the phpMyAdmin session to end.

Thanks!

I'm trying to do P2V with a Debian powered-on source. Everything works perfectly up until the point of selecting destination.

It states that the destination type is VMware Infrastructure virtual machine.

It asks for the server details and along the right it states that supported VMware Infrastructure products include VMware vCenter Server 2.0, 2.5 and 4.0. Great, I thought, because I'm running VMware vCenter Server 4.0.1 on this machine.

So I try to specify the details of my machine but I get any one of a few errors:

• Timeout
• Unable to recognise the server type or version
• Target machine actively refused the connection

What confuses me the most is that I'm using the same details of the server I connected to in the first place, therefore I know that it can connect to the server and it is running.

The server is running on my laptop, the agent is running on the Linux machine. I get this same error whether I use the client on my laptop or the Linux machine itself!

Any ideas? Do I need another product running to be the 'destination'?