The Heap™ – Consultancy ©®

« first day (1334 days earlier) ← previous day next day → last day (3520 days later) »

Faheem Mitha

8:17 AM

Hi everyone. PostgfeSQL has the psql interpreter. MySQL has mysql. Is that the best available?

4 hours later…

Aaron Bertrand

12:17 PM

Seriously, now people are going to go and edit every single post with an image in it, and make the URLs "protocol agnostic"?

e.g. changing i.stack.imgur.com/gCIix.png to //i.stack.imgur.com/gCIix.png

2 hours later…

James

1:50 PM

Does that work without an absolute reference that the 'protocol agnostic' URL is relative to? E.g.
[link text](//i.stack.imgur.com/gCIix.png "test")

... doesn't seem to work.

I guess it always would in a link on a web page, though

Aaron Bertrand

It may only work when you use the [1] notation in a post. See this edit. Seems frivolous to me.

My comment:

@hjpotter92 I sincerely hope you don't plan to suggest edits on every single post with images just to make the URL protocol agnostic. This is a lot of busy work for reviewers for what real gain? — Aaron Bertrand ♦ 11 mins ago

Only really useful for img src, too, since the whole reason is if I'm viewing the site under https:// and the images are http://, I'm going to have security warnings about mixed content (but who cares, really, and why am I viewing Stack Overflow in https?). Doesn't matter for links because I'm clicking to a new page (and you won't always have any idea if the destination supports SSL).

ConcernedOfTunbridgeWells

2:47 PM

@swasheck What's your capacity plan for data volumes?

A DL980 is a fairly expensive piece of kit - especially the SQL server licensing for 80 cores.

Faheem Mitha

Can anyone suggest a small tutorial for mysql for someone who is alrready somewhat familiar with postgresql? Just to get going?

ypercube

3:29 PM

@ConcernedOfTunbridgeWells is the plan for next Friday still on?

@FaheemMitha If you have worked with Postgres, you could take a project/database from that and try it in MySQL. And see where it breaks. You'll learn a lot about various differences by trying to fix it.

Faheem Mitha

3:51 PM

@ypercube I'm literally just trying to get started. How do I create a db in Mysql, on Debian? That is what I need to do at the moment. There are those pesky access issues you tend to forget about, creating the db user. That kind of low level crap.

A couple of pages of handholding by a MySQL user would be helpful.

ypercube

@FaheemMitha There are many tutorials on the web. try this for start: digitalocean.com/community/tutorials/…

Faheem Mitha

@ypercube heh, I just started looking at that. is it good/correct?

"After entering the root MySQL password" What is that?

ypercube

@FaheemMitha I don't see this in that page.

I suppose you have installed mysql and you have the root password for mysql. Right?

Faheem Mitha

@ypercube The former is true, the latter is not. I haven't set any root password. I read on the net that if you don't set it, it is blank. But that does not seem to be working here. Checking to see what the debian-specific docs are, if anything.

I guess I should try and find some official mysql docs.

ypercube

you are on Debian or Ubuntu?

Faheem Mitha

4:01 PM

@ypercube Debian wheezy.

Never mind, I'll figure it out.

I think. If I can't I may be back.

ypercube

You can either find it or reset it, if you don't know it.

If you try to log with: mysql -u root

what happens?

Faheem Mitha

@ypercube Ok. Turns out I hadn't installed the server. When I did, debconf pops up with a password request. Doh. Sorry about that.

Faheem Mitha

4:20 PM

I'm getting a fail on start

[FAIL] Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.5 (--configure):
subprocess installed post-installation script returned error exit status 1

This is in a chroot. Does mysql need any particular device or suchlike to get going?

ypercube

@FaheemMitha No idea. I don't mess with debian installs often.

Faheem Mitha

@ypercube Ok

ypercube

It seems it has been isnstalled but the sartup procedure throws this error

You can ask a question at SuperUser site. This seems similar: superuser.com/questions/618358/… (but not really sure if it applies to your case)

Faheem Mitha

4:54 PM

@ypercube Thanks. Trying outside the chroot in main system now. Seem to be seeing the same error.

But there was a downgrade from 5.6 involved.

Nuking everything and starting over.

ypercube

5:05 PM

try uninstalling all mysql. Then remove the /var/lib/mysql/ directory. Then reinstall.

Faheem Mitha

@ypercube: I just did that.:-) Possible it doesn't like my password for some reason. It popped up a message saying it couldn't set the password. But I had just nuked (--purge) every mysql related.

Let me try a different password. Does mysql have an special password requirements?

ypercube

no, i don't think so.

Faheem Mitha

Unable to set password for the MySQL "root" user
An error occurred while setting the password for the MySQL administrative user. This may have happened because the account already has a password, or
because of a communication problem with the MySQL server.
You should check the account's password after the package installation.
Please read the /usr/share/doc/mysql-server-5.5/README.Debian file for more information.

That's the error message I got.

Oh, I see

140830 22:33:37 [ERROR] Unknown/unsupported storage engine: InnoDB
140830 22:33:37 [ERROR] Aborting

Hmm, what is going on here?

Here is the full error I'm a little out of my depth here, but it is probably something obvious

140830 22:33:37 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
140830 22:33:37 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140830 22:33:37 [Note] Plugin 'FEDERATED' is disabled.
140830 22:33:37 InnoDB: The InnoDB memory heap is disabled
140830 22:33:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins

ypercube

@FaheemMitha See: serverfault.com/questions/104014/…

Faheem Mitha

5:23 PM

@ypercube Thanks. Maybe I set some config locally somewhere, and forgot about it. Checking now.

ypercube

Trty the answer ther:
> 5. Delete both log files.
> 6. Start MySQL. It will complain about the lack of log files, but it'll create them and all will be well.

Faheem Mitha

Indeed, I have a my.cnf, Mon Aug 05 23:12:22 2013. Wonder what I was doing.

that was the datestamp on the etckeeper commit

Funny, /etc/mysql/debian.cnf says automatically generated, do not touch, but was left behind when I purged all the mysql packages.

Weird

Shouldn't autogenerated files be purged too?

Purged all packages again. Renamed this .cnf files. Still same errors.

where should installation problems go? Serverfault?

I see that there are some files in /var/lib/mysql. Is that where the database is stored?

@ypercube Um, which log files are those?

everything in /var/lib/mysql is still there. shouldn't it get rid of that?

Funny defn of purge this package has. Leaves loads of stuff lying around, then freaks out about it.

Ok, this time it worked. Sheesh.

ypercube

5:52 PM

Yes, the databases are usually stored in /var/lib/mysql/

The ib_logfile are InnoDB log files.

Faheem Mitha

6:10 PM

@ypercube Oh, I see /var/lib/mysql/ib_logfile0 is what is causing the problem?

ypercube

It could be one of the reasons. The real reason is that you have messed it up ;)

And I don't know what exactly you did, what was the previous (if any) installation, or how you did it.

But if you get that error when trying to start mysql (InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! )

you can try to erase these 2 files and then start.

1 hour later…

Faheem Mitha

7:37 PM

@ypercube I beg to differ. No messup.

I had 5.6 installed earlier. I guess it couldn't cope gracefully with a downgrade.

Anyway, like I said, fixed now.

When I did a purge, I didn't realise there were still files laying around.

« first day (1334 days earlier) ← previous day next day → last day (3520 days later) »

all rooms