Drupal 7 install with lots of warnings

One of the many reasons I'll never host anything at Godaddy is that their permissions are horribly mangled between their proprietary interface and the real, underlying system that is accessible via FTP.

You need to call their support line and have them untangle this for you.

this is bad for drupal

The one click install for this does not work .

Its a shame that a new person trying drupal for first time......GETS

1 ERRORS are the first thing you see when you load for the first time

2 You uninstall try again..... NOPE..You uninstall try again.... NOPE..You uninstall try again.... NOPE..You uninstall try again.... NOPE..I tried 5 times.....

3 YOU GIVE UP ON DRUPAL go try for a solution that works.

4 This community should BAN godaddy from offering drupal as ANYONE who installs on their servers will have a bad experience and give up on you...

5.HAVE A CLEAR SOLUTION POSTED ON THIS FORUM if there is one I can not find it...

Anyone in this situation has options

1 Try new hosting.. OK I will move my host,domain,email,etc to try to get a failed product to work? NOT
2 move on..CHECK..

Sorry for you Im sure you all worked very hard on drupal

Its a bit like serving steak on a cow pat..

NOTE this is not me having a go at Drupal

I'm responding due to the very high rank on Google of this common question (and to help those that have misinterpreted community support or misplaced their manners (read, digest http://drupal.org/forum-posting)).

Programmer-by-day or not, make a reasonable attempt to parse the given warning or message. It may turn out that the solution is not even Drupal-specific in scope. When in doubt, respond politely and don't abuse grammar out of frustration.

That aside, the error/warning messages usually provide better starting information for troubleshooting than a search engine.

For instance:
* Warning: opendir(/tmp/update-cache) failed to open dir: Permission denied in DrupalLocalStreamWrapper->dir_opendir()...blah blah blah....

Suggests an error with /tmp on the local linux filesystem. What does "permission denied" mean in any context? Warnings such as these can be easy traced. To elaborate:

Warning: opendir(sites/all/modules/captcha): failed to open dir: Permission denied in file_scan_directory() (line 1975 of /var/www/example.org/blog/includes/file.inc).
Warning: opendir(sites/all/modules/admin_menu): failed to open dir: Permission denied in file_scan_directory() (line 1975 of /var/www/example.org/blog/includes/file.inc).

Cancel out some of the common factors on the lines:
Warning: opendir(sites/all/modules/captcha)
Warning: opendir(sites/all/modules/admin_menu)

Looks like a warning for "opendir" on sites/all/modules, with captcha and admin_menu being data points.
Let's not look at the line of code from the file that was being reported - variables can be annoying to chase and who says you're sold enough on this CMS-du-jour to spend the time tracking errors in code?

Anyway, Drupal seems to complain about various modules that we assume should work. Oh, and Drupal is telling you that it doesn't have permissions to do something to the file.

Start with the easiest and least insecure solution, telling your computer to let your webserver read a file.
In other words, our solution:
-Check that Apache (or whatever server) can read the files in the directory sites/all/modules. This is as simple as setting the file owner as your webserver user or putting your webserver in a group with permissions to read those files.

I hit this problem when I changed user groups on my seldom-used hosting box. I solved this by giving the Drupal directories to the group "drupalweb" with the group members of myself and www-data.

For me the issue was I was incorrectly parsing which directory needed to be fixed.

It wasn't tmp. It was sites/modules.