Announcement

Collapse
No announcement yet.

Pruning 9000+ Members - Invalid Action Specified

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Zachery
    replied
    As far as I know, if you're getting the invalid action specified, some of the required data was not passed along. This is normally an issue with the server truncating the post request, or not getting all of it.

    Leave a comment:


  • snakes1100
    replied
    Adjust your input variables via php.ini

    Leave a comment:


  • MikeF
    replied
    Originally posted by snakes1100 View Post

    You are incorrect, this is a simple fix & has been posted correctly numerous times, its not a memory issue, nor is it related to mysql settings, they can be a factor if your trying to prune say 50,000 at a time though.

    This issue is also related to suhosin if its installed.

    This issue is related to input variables & their lengths, which is php.

    Vbulletin, should correct the error msg.
    I am using a server without Suhosin installed at all and its still dropping the error with a phrase in AdminCP from user.php:

    Code:
                           define('CP_REDIRECT', "user.php?do=pruneusers" .
                                    "&usergroupid=" . $vbulletin->GPC['usergroupid'] .
                                    "&daysprune=" . $vbulletin->GPC['daysprune'] .
                                    "&minposts=" . $vbulletin->GPC['minposts'] .
                                    "&joindate=" . $vbulletin->GPC['joindate'] .
                                    "&order=" . $vbulletin->GPC['order']
                            );
    
                            print_stop_message('invalid_action_specified');
    and

    Code:
    // ############################# do prune users #########################
    if ($_REQUEST['do'] == 'dodeleteusers')
    The error is dropped in the code itself with the stop_message. Why its still doing it I don't know. Its not like 20,000 its almost like its hard wired. Here is what I think: having deleted almost 15,000 users, almost manually, earlier last night, some had been listed as banned but were listed in the primary usergroup COPPA Users Awaiting Moderation when viewing their profile data. When checking this usergroup field and even trying to move these users into a usergroup with a SQL query I ended up seeing 0 results for anyone being listed in this usergroup,anyone being in a null primary usergroup, etc. While I have not had the patience to fully examine the problem because this is a live production site, I routinely found user data listed in the prune user function of users without a usergroup listed under their username. (You are about to execute pruneusers and see the enormous list upon you - let me clarify some have no usergroup listed under the username itself very rarely).

    In some way or another there was some kind of corruption with these fields, perhaps between versions. Also, are you saying something in the table should be a long INT when its not or what exactly? I would think that lends itself to a database problem and not mutually exclusive to PHP. However if you know if the "simple fix has been posted correctly numerous times" what is it exactly?

    Leave a comment:


  • snakes1100
    replied
    Originally posted by MikeF View Post
    Invalid Action is a message relayed by vBulletin code and not any PHP or MySQL setting that I am aware of. Most of this thread is incorrect information, as other threads on the subject. "You should fix your server configuration and php.ini" but no indication as to where. Guess what: set MySQL timeout to unlimited, memory to 24GB, and all PHP and socket timeouts to 9999999 and the message still appears. It is a limit of vBulletin and should be addressed as such.
    You are incorrect, this is a simple fix & has been posted correctly numerous times, its not a memory issue, nor is it related to mysql settings, they can be a factor if your trying to prune say 50,000 at a time though.

    This issue is also related to suhosin if its installed.

    This issue is related to input variables & their lengths, which is php.

    Vbulletin, should correct the error msg.
    Last edited by snakes1100; Mon 22nd Jul '13, 9:33pm.

    Leave a comment:


  • MikeF
    replied
    Invalid Action is a message relayed by vBulletin code and not any PHP or MySQL setting that I am aware of. Most of this thread is incorrect information, as other threads on the subject. "You should fix your server configuration and php.ini" but no indication as to where. Guess what: set MySQL timeout to unlimited, memory to 24GB, and all PHP and socket timeouts to 9999999 and the message still appears. It is a limit of vBulletin and should be addressed as such.

    Leave a comment:


  • Ion Saliu
    replied
    I did have a similar problem:

    https://www.vbulletin.com/forum/show...ers-in-AdminCP

    In my experience, I wasn’t able to delete 1000 or more users in a batch. Now, my forum is not that old (since September 2010). I started pruning when the number of “members” reached 13,000. I realized that 90% of them were spammers.

    There is a failed business on the Internet to create user profiles in many, many forums. The scammers “think” that the search engines would improve a website’s ranking because there are lots of backlinks pointing to the website. NOT! Au contraire, Google started to severely punish the websites who resort to such SEO tactics!

    I’m pretty sure now that 75% to 90% of all users, in any forum in the world, are spammers created mainly by spambots.

    So, I resolved my problem by setting the days without a login to 1000. If your forum is very old, figure out its age in days. Set days without a login to the age of your forum. Hopefully, you’ll get a number of total users under 1000. If not, try first one group at a time. Start with users awaiting email verification; then banned users

    It is very easy for me now, as I keep total members under 1000. I just did a pruning operation before posting this reply.

    It could be that 1000 users to prune is the maximum limit of a pruning batch.

    Best of luck!

    Ion Saliu
    Board Maintenance: Users Pruned for Inactivity

    Leave a comment:


  • NorCal
    replied
    same problem changing date does not solve it

    also 4.2pl3
    I did an Impex import which set about 10,000 users to the same date: 1970. Even if I set the date to thousands of days, it is still going to return the same number.

    Originally posted by Lynne View Post
    Then try 400 days, or 500 days. You should be able to find some number to enter that will make the group smaller.

    Leave a comment:


  • Lynne
    replied
    Then try 400 days, or 500 days. You should be able to find some number to enter that will make the group smaller.

    Leave a comment:


  • Snotek
    replied
    There is no way to do this. The pruning mechanism is not set up to apply a date range. So I can only search for "Registered Users who have not logged in for 180 days." This query still gives me 9300+ users.

    Leave a comment:


  • Lynne
    replied
    Just do a Prune, and set the Has not Logged on for xx days to different numbers to get a smaller batch to delete.

    Leave a comment:


  • Snotek
    started a topic [Forum] Pruning 9000+ Members - Invalid Action Specified

    Pruning 9000+ Members - Invalid Action Specified

    While trying to prune some 9500 members I get the error "Invalid Action Specified" and cannot continue. I did some searching and have found threads on this site back to 2007 or so identifying the same issue which is still apparently unresolved. The "best answers" I could find are a) your server cannot handle it and b) do smaller batches.

    Neither of these answers are acceptable for mass prune jobs such as these, and besides would require a lot of admin time to manually select bulk users like that - especially when there is a built-in system for doing just this type of activity.

    I am currently running vB 4.2.0PL3 on a dedicated server that I assure you has enough horsepower to easily accomplish this task.

    While a customized SQL query could also do the job directly from the database I'm unsure as to the greater ramifications of this action, if any, and is also not an acceptable answer.

    Can someone from vBulletin please take a look at this issue?

Related Topics

Collapse

Working...
X