Jump to content

Welcome to the Freedomain Radio Message Board


Sign In 

Create Account
If you're interested in joining the philosophical discussion, click "sign in" or "create account" on the right of the page. If you're creating a new account, please be sure to include an explanation as to why you're interested in joining the message board community. This verification requirement is included to cut down on possible troll and spam accounts.

If you have supported Freedomain Radio financially and would like immediate access to the message board - or - your donation status is incorrect, please contact Michael at operations@freedomainradio.com with your information and the situation will be addresses ASAP.
 
Guest Message by DevFuse

Sunday April 20th, 2014: Sunday Call In Show at 10am Eastern

Wednesday April 23rd, 2014: No Call In Show

Thursday and Friday April 24-25th, 2014: The Next Web Conference in Amsterdam

Saturday April 26th, 2014: Freedomain Radio Meet-Up in Amsterdam

Sunday April 27th, 2014: No Call In Show


56 Philosopher King files - 71 Gold files - 39 Silver files - 50 Bronze files


Update: A new silver level file on Peer Influence and Envy has been added! Click here to donate if you'd like access to the various premium sections. If your donator status is incorrect, please contact Michael at operations@freedomainradio.com with the relevant information and it will be corrected as soon as possible.

Photo

There appears to be an error with the database.

db error posting

  • Please log in to reply
6 replies to this topic

#1
MerlinSilk

MerlinSilk

  • 3 posts

I get an error "There appears to be an error with the database" when trying to post a new 'Isssue' -

the issue/suggestion I wanted to get off my chest is:

 

I ran into a discussion about minimum wages today and remembered there was a podcast a while ago about this subject. I tried to find this to throw into the discussion - but was unable to find it. I looked through the youtube channel first - nothing came up for a search for that keyword.

Then I went to the main site, no luck,

then I finally logged into the forums, again no go.

With this huge amount of content I am sure there should be somethnig for me to find - but no, so I believe, we need a better indexing/tagging functionality for the site.

I am sure this could be handled with crowd sourcing - if every subscriber gets a chance and request to add a few tags (including time index for audio/video) for everything she/he digests, it should be a rather painless task to get a good index of all of Stefans content.


  • 0

#2
Bardan

Bardan

  • 94 posts

I'm not up with the play, but I understand work is in motion to do this. Folk are going through each podcast tagging keywords to minutes as part of an on-going project which started in the last few months. I was going to help out myself but my work in taking notes isn't that specific.


  • 0

Skype: Clarkvillian


#3
MerlinSilk

MerlinSilk

  • 3 posts

that is good news!


  • 0

#4
FriendlyHacker

FriendlyHacker

  • 251 posts

What is the error code you see? Screenshot? I'm not a volunteer here or anything, but probably know how to fix it.


  • 0

#5
Kevin Beal

Kevin Beal

    :)


  • 1404 posts

301: Price Controls and the Minimum Wage

 


As far as I understand it there are plans to improve this sort of thing, but it's a hell of a lot of work and there weren't that many people volunteering to help out. 

 

In the meantime I would suggest two things, first to google terms like "freedomain radio [my keyword]" (as the kind of results you want are on several different sites), and second to start tagging and time stamping podcasts. There are a decent number of finished ones I think, so I'd ask Mike (MMD) what podcasts would be the best to timestamp (I think he has an order to things he's working on).

 

The Why you are Unemployed series also touches on minimum wages, and I'm sure it's come up tangentially in different sunday shows and listener conversations.


What is the error code you see? Screenshot? I'm not a volunteer here or anything, but probably know how to fix it.

 

If the error actually says "There appears to be an error with the database" it's a vague IPBoard generated error that shows up when the database migration from the old software wasn't exactly perfect. More here. Which doesn't make a lot of sense since there was no "issues tracker" in the old system. Maybe JamesP is working on something...?


  • 1

"There is no law, no compulsion, no law of physics or man that is preventing you from living the life that you want" - Stef (The Greatest Gift in the Entire Universe)


#6
MerlinSilk

MerlinSilk

  • 3 posts

thank you so much for the link!
There was no error code, just something like Oops, something wrong with ... sorry did not take a screenshot.


  • 0

#7
FriendlyHacker

FriendlyHacker

  • 251 posts

Check your server error log, it will display the specific error message you need to fix it, though I suspect this might have to do with missing tables, specifically innodb tables.

Try running this query on phpmyadmin:

(Maybe only one table is missing though, so try one at time)

 

First select the mysql database (it's probably actually called mysql)

CREATE TABLE `innodb_index_stats` (
  `database_name` varchar(64) COLLATE utf8_bin NOT NULL,
  `table_name` varchar(64) COLLATE utf8_bin NOT NULL,
  `index_name` varchar(64) COLLATE utf8_bin NOT NULL,
  `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `stat_name` varchar(64) COLLATE utf8_bin NOT NULL,
  `stat_value` bigint(20) unsigned NOT NULL,
  `sample_size` bigint(20) unsigned DEFAULT NULL,
  `stat_description` varchar(1024) COLLATE utf8_bin NOT NULL,
  PRIMARY KEY (`database_name`,`table_name`,`index_name`,`stat_name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=0;

CREATE TABLE `innodb_table_stats` (
  `database_name` varchar(64) COLLATE utf8_bin NOT NULL,
  `table_name` varchar(64) COLLATE utf8_bin NOT NULL,
  `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `n_rows` bigint(20) unsigned NOT NULL,
  `clustered_index_size` bigint(20) unsigned NOT NULL,
  `sum_of_other_index_sizes` bigint(20) unsigned NOT NULL,
  PRIMARY KEY (`database_name`,`table_name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=0;

CREATE TABLE `slave_master_info` (
  `Number_of_lines` int(10) unsigned NOT NULL COMMENT 'Number of lines in the file.',
  `Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the master binary log currently being read from the master.',
  `Master_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The master log position of the last read event.',
  `Host` char(64) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '' COMMENT 'The host name of the master.',
  `User_name` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The user name used to connect to the master.',
  `User_password` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The password used to connect to the master.',
  `Port` int(10) unsigned NOT NULL COMMENT 'The network port used to connect to the master.',
  `Connect_retry` int(10) unsigned NOT NULL COMMENT 'The period (in seconds) that the slave will wait before trying to reconnect to the master.',
  `Enabled_ssl` tinyint(1) NOT NULL COMMENT 'Indicates whether the server supports SSL connections.',
  `Ssl_ca` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The file used for the Certificate Authority (CA) certificate.',
  `Ssl_capath` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The path to the Certificate Authority (CA) certificates.',
  `Ssl_cert` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the SSL certificate file.',
  `Ssl_cipher` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the cipher in use for the SSL connection.',
  `Ssl_key` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the SSL key file.',
  `Ssl_verify_server_cert` tinyint(1) NOT NULL COMMENT 'Whether to verify the server certificate.',
  `Heartbeat` float NOT NULL,
  `Bind` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'Displays which interface is employed when connecting to the MySQL server',
  `Ignored_server_ids` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The number of server IDs to be ignored, followed by the actual server IDs',
  `Uuid` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The master server uuid.',
  `Retry_count` bigint(20) unsigned NOT NULL COMMENT 'Number of reconnect attempts, to the master, before giving up.',
  `Ssl_crl` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The file used for the Certificate Revocation List (CRL)',
  `Ssl_crlpath` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The path used for Certificate Revocation List (CRL) files',
  `Enabled_auto_position` tinyint(1) NOT NULL COMMENT 'Indicates whether GTIDs will be used to retrieve events from the master.',
  PRIMARY KEY (`Host`,`Port`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Master Information';

CREATE TABLE `slave_relay_log_info` (
  `Number_of_lines` int(10) unsigned NOT NULL COMMENT 'Number of lines in the file or rows in the table. Used to version table definitions.',
  `Relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the current relay log file.',
  `Relay_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The relay log position of the last executed event.',
  `Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the master binary log file from which the events in the relay log file were read.',
  `Master_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The master log position of the last executed event.',
  `Sql_delay` int(11) NOT NULL COMMENT 'The number of seconds that the slave must lag behind the master.',
  `Number_of_workers` int(10) unsigned NOT NULL,
  `Id` int(10) unsigned NOT NULL COMMENT 'Internal Id that uniquely identifies this record.',
  PRIMARY KEY (`Id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Relay Log Information';

CREATE TABLE `slave_worker_info` (
  `Id` int(10) unsigned NOT NULL,
  `Relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
  `Relay_log_pos` bigint(20) unsigned NOT NULL,
  `Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
  `Master_log_pos` bigint(20) unsigned NOT NULL,
  `Checkpoint_relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
  `Checkpoint_relay_log_pos` bigint(20) unsigned NOT NULL,
  `Checkpoint_master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
  `Checkpoint_master_log_pos` bigint(20) unsigned NOT NULL,
  `Checkpoint_seqno` int(10) unsigned NOT NULL,
  `Checkpoint_group_size` int(10) unsigned NOT NULL,
  `Checkpoint_group_bitmap` blob NOT NULL,
  PRIMARY KEY (`Id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Worker Information';


  • 0





Also tagged with one or more of these keywords: db, error, posting

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users