Zenexer's questions

I need to recover data from an old 5.6.x snapshot. With a little bit of tinkering, I managed to get the 5.6.x snapshot restored on an m3.xlarge instance (any instance type other than m3.* won't work). I then successfully upgraded from 5.6.x to the latest 5.7.x.

The next step was to go from 5.7.x to 8.0.x. Each time I tried to perform the upgrade, RDS would claim it was "Upgrading", but it would return the "Available" state quickly, and it would be back to 5.7.x, with no visible errors in the console.

How do I upgrade it to 8.0.x?

I'm using nginx version 1.4.6.

I'm having trouble getting map to work. I have something like this:

http {
    map $arg_f $forum {
        default 0;
        1 2;
    }

    # ...

    server {
        # ...

        location = /old.php {
            if ($forum) {
                return 301 /forums/$forum/;
            }
            return 494;
        }

        # ...
    }

    # ...
}

Here's what I get with nginx -t:

nginx: [emerg] unknown "forum" variable

The goal is to map old URIs to new URIs. The catch is that some of the numeric forum IDs have changed. I'd like to handle this in Nginx, so I'm willing to resort to lua if there's no other easy way. I'm open to alternative solutions as long as they're elegant, but I'd like to know why map isn't working here. Is it because the rewrite module doesn't query maps, at least in 1.4?

I'm running a pretty minimal MySQL cluster with configuration pretty much taken straight from the documentation. The data nodes are connecting fine, but the management server refuses to accept the API nodes. Here's what happens:

INFO     -- Node 2: Initial start, waiting for 3 to connect,  nodes [ all: 2 and 3 connected: 2 no-wait:  ]
INFO     -- Node 3: Initial start, waiting for 2 to connect,  nodes [ all: 2 and 3 connected: 3 no-wait:  ]
WARNING  -- Failed to allocate nodeid for API at 10.0.42.2. Returned error: 'No free node id found for mysqld(API).'
WARNING  -- Failed to allocate nodeid for API at 127.0.0.1. Returned error: 'No free node id found for mysqld(API).'

show from ndb_mgm outputs this:

Connected to Management Server at: localhost:1186
Cluster Configuration
---------------------
[ndbd(NDB)]     2 node(s)
id=2    @127.0.0.1  (mysql-5.6.14 ndb-7.3.3, starting, Nodegroup: 0)
id=3    @10.0.42.2  (mysql-5.6.14 ndb-7.3.3, starting, Nodegroup: 0)

[ndb_mgmd(MGM)] 1 node(s)
id=1    @127.0.1.1  (mysql-5.6.14 ndb-7.3.3)

[mysqld(API)]   2 node(s)
id=4 (not connected, accepting connect from any host)
id=5 (not connected, accepting connect from any host)

Here's my.cnf--nothing particularly interesting:

[mysqld]

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

language=english

ndbcluster

[mysql_cluster]
ndb-connectstring=localhost

The only API-related configuration in config.ini is this:

[mysqld]
[mysqld]

There's no [mysqld default] section. I've tried setting hostnames.

I've tried both ndbd --reload and ndbd --initial, with appropriate restarts.

Update

It looks as though neither data node is listening on port 2202 based on the output of netstat -nl. Since neither is listening, they can't connect to each other, and the cluster is never ready for API nodes to join. What could be preventing this?

I'm trying to add a new SATA drive (SSD) as a local SR. XenServer may have seen the drive before, but I don't recall every doing anything with it. I'm attempting to run this command:

xe sr-create content-type=user device-config:device=/dev/disk/by-id/scsi-SATA_OCZ-VERTEX2_3.5OCZ-9G0363DTJ6JSCBJ1 name-label="Local Storage SSD 1" type=ext

A new SR appears in XenCenter for a split second (I don't have time to read what it says), then I receive an error:

The SR operation cannot be performed because a device underlying the SR is in use by the host.

Here's the log from /var/log/SMlog, minus the timestamps:

lock: creating lock file /var/lock/sm/20d58608-bebb-64a8-0cae-d3d36b3f2d7d/sr
lock: acquired /var/lock/sm/20d58608-bebb-64a8-0cae-d3d36b3f2d7d/sr
sr_create {'sr_uuid': '20d58608-bebb-64a8-0cae-d3d36b3f2d7d', 'subtask_of': 'DummyRef:|7f60f5ae-9a40-6550-f587-c28cbe4c4926|SR.create', 'args': ['0'], 'host_ref': 'OpaqueRef:3d304cee-dac2-2eb3-80d9-6e8a166c1135', 'session_ref': 'OpaqueRef:c5a8fc26-cec6-eeb9-09ed-f36604bdfc77', 'device_config': {'device': '/dev/disk/by-id/scsi-SATA_OCZ-VERTEX2_3.5OCZ-9G0363DTJ6JSCBJ1', 'SRmaster': 'true'}, 'command': 'sr_create', 'sr_ref': 'OpaqueRef:7dd401ca-b41d-b606-6612-3dd3919b0773', 'local_cache_sr': '16cbaddd-05db-11b9-d5f9-5933d3192243'}
['sginfo', '-s', '/dev/sdb']
  pread SUCCESS
['scsi_id', '-g', '-s', '/block/sdb']
  pread SUCCESS
['/usr/sbin/vgs', 'XSLocalEXT-20d58608-bebb-64a8-0cae-d3d36b3f2d7d']
FAILED in util.pread: (rc 5) stdout: '', stderr: '  Volume group "XSLocalEXT-20d58608-bebb-64a8-0cae-d3d36b3f2d7d" not found
'
Raising exception [16, The SR device is currently in use [opterr=Device /dev/disk/by-id/scsi-SATA_OCZ-VERTEX2_3.5OCZ-9G0363DTJ6JSCBJ1 in use, please check your existing SRs for an instance of this device]]
lock: released /var/lock/sm/20d58608-bebb-64a8-0cae-d3d36b3f2d7d/sr
***** generic exception: sr_create: EXCEPTION SR.SROSError, The SR device is currently in use [opterr=Device /dev/disk/by-id/scsi-SATA_OCZ-VERTEX2_3.5OCZ-9G0363DTJ6JSCBJ1 in use, please check your existing SRs for an instance of this device]
  File "/opt/xensource/sm/SRCommand.py", line 106, in run
    return self._run_locked(sr)
  File "/opt/xensource/sm/SRCommand.py", line 153, in _run_locked
    return self._run(sr, target)
  File "/opt/xensource/sm/SRCommand.py", line 278, in _run
    return sr.create(self.params['sr_uuid'], long(self.params['args'][0]))
  File "/opt/xensource/sm/EXTSR", line 188, in create
    lvutil.createVG(self.root, self.vgname)
  File "/opt/xensource/sm/lvutil.py", line 302, in createVG
    opterr=('Device %s in use, please check your existing ' \
  File "/opt/xensource/sm/xs_errors.py", line 49, in __init__
    raise SR.SROSError(errorcode, errormessage)

lock: closed /var/lock/sm/20d58608-bebb-64a8-0cae-d3d36b3f2d7d/sr

Update

I did a fresh install of the latest XenServer release (6.2.0). The disk was not in the server during the installation. Thin provisioning (ext3) was used.

After the installation completed, I immediately added the disk and rebooted the server. I then ran the following command:

xe sr-create name-label='Local SSD 1' device-config:device=/dev/disk/by-id/scsi-SATA_OCZ-VERTEX2_3.5OCZ-9G0363DTJ6JSCBJ1 type=ext

This resulted in the same error.